Repository size . . . is this right

[Matt Nordhoff]

Robert Collins wrote:
> On Wed, 2008-12-10 at 17:33 +0900, Stephen J. Turnbull wrote:
> 
>>  > I'd support having 'bzr pack && bzr pack' leave an empty
>>  > obsolete_packs directory. I also completely agree that the current
>>  > behaviour confuses people and thats *not good*. However, safety is
>>  > really important too.
>>
>> I think there should be a separate command, bzr garbage-collect, or
>> maybe even bzr clean, perhaps with options for how aggressively it
>> classifies stuff as garbage.
> 
> I'd like to add a gc command for sure. The contents of obsolete_packs
> really are obsolete; every bit of data in there is also in packs/ - its
> solely a reflection of the limitations upon userspace saying 'make sure
> these files are on physical media' that cause it to be used as it is.
> Exposing 'clean obsolete_packs' as 'gc --fast' could be good, but I
> would like to have some way where the duplicate data is removed more
> promptly than it does today, automatically. 
> 
> -Rob

What about something like this? Whenever the repository is modified
(commit, pull, whatever), check if the obsolete_packs have been there
for more than an hour, and if so, delete them. That should be enough
time for a disk sync.
--