[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: On adding size info to Packages files [very long]



Manoj Srivastava <srivasta@datasync.com> writes:

> Hi,
> >>"Brederlow" == Brederlow  <goswin.brederlow@student.uni-tuebingen.de> 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 ;-)

In case you changed something, you have to run the symlink check
again. When you update a Package it will from now on trimm the tree to 
the correct dirs. The calculation of space needed/gained for an update 
would then be wrong once. Since the data is only 100K, lets keep it
all.

May the Source be with you.
			Mrvn


--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: