Hi, >>"Brederlow" == Brederlow <[EMAIL PROTECTED]> writes:
Brederlow> I mean, that when a package is installed, that the Brederlow> recorded du tree (which is needed to calculate the size Brederlow> increase/decrease for updates) could be trimmed to what Brederlow> the users system reflects. The users system setup should Brederlow> be scanned and kept in a status file for speed reasons Brederlow> (trying all dirs for symlinks takes time) and then Brederlow> trimming should be fairly easy and save a lot of space. It Brederlow> would save the more the smaler (less partitions) the Brederlow> system is. You have a point. Hmm. The sizes file I haegv been talking about is analogous to the Packages/available file; we also need the analogue of the Status file, and it may make sense to coalesce the data down in the Sizes.installed file. However, that would make the handling of newly created partitions impossible (I created /usr/lib when my /usr partition was in danger of running out of space). Once coalesced down, there is no easy way of recreating the data; and since the installed Sizes file is of the order of 100k compressed, and the savings are unlikly to be more than 30-40k, I still think we should not discard data. Correct operation is worth more than 40k ;-) manoj -- I think a good gift for the President would be a chocolate revolver. And since he's so busy, you'd probably have to run up to him real quick and hand it to him. Manoj Srivastava <[EMAIL PROTECTED]> <http://www.datasync.com/%7Esrivasta/> Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]