Make the # of backups at each level configurable

[assistcontrol]

I'm curious whether anybody else is into this idea. The defaults are so completely sensible that I'm not sure anybody else would be keen to change them.

A setting of "0" means to keep indefinitely.

With it now being done three times (adding in yearly), the
deletion loop becomes repetitive. This commit factors it
out into a function.

[alexjurkiewicz]

Using a common function for the deletion loop seems like a good idea even if the parameters aren't exposed.

[assistcontrol]

I'm gradually working on a copy model that will obviate the need for the loop. It'll do a daily backup every time, and then use tarsnap's copy function to create monthly/yearly backups as needed.

[alexjurkiewicz]

I saw that comment, sounds clever. I've just pushed a "fix" for Travis too, which should help.

…

On Tue, 11 Jun 2019 at 10:45, Adam Weinberger ***@***.***> wrote: I'm gradually working on a copy model that will obviate the need for the loop. It'll do a daily backup every time, and then use tarsnap's copy function to create monthly/yearly backups as needed. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#31?email_source=notifications&email_token=AAC4U5MJFM23NIXEBJXXC7DPZ3YRNA5CNFSM4HWZPHXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXLTN4I#issuecomment-500643569>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAC4U5IZZUBM32YRQA3XOOTPZ3YRNANCNFSM4HWZPHXA> .

[assistcontrol]

I'm gradually working on a copy model that will obviate the need for the loop. It'll do a daily backup every time, and then use tarsnap's copy function to create monthly/yearly backups as needed.

That's a lie. The copy model only affects backup, not pruning. This PR is completely separate.