Xavier wrote:
On Thu, Feb 26, 2009 at 4:11 AM, Allan McRae <allan@archlinux.org> wrote:
One comment that is moderately related to this. Should there be a mechanism to inspect the deltas are remove the ones that are no longer necessary? I.e. deltas with a broken chain, deltas who chain download will be bigger than the package. Should that be a job of repo-add when adding a new delta or a separate script?
I don't know, that seems neat but maybe too much complexity, I am not sure. Finding out how deltas could/should be managed has always been a big issue to me, how/when they are added, how/when they are removed.
Hi Guys I was just getting into understanding the code to see what I could do to get this going myself. Thank you, Xavier - I think it would have taken me a week or 2 to put all this together and likely not nearly good enough for Allan to be saying mostly good things about it. ;) Now that you mentioned it, other than broken chains and deltas bigger than "deltaless" downloads, what other criteria are there for delta removal? I can only think of disk space - though this is not likely to be an issue. Also on that note, other than this new code breaking the chain, how would a chain be broken?