On Wed, Jan 26, 2011 at 10:38:01AM -0500, Michael K. Johnson wrote: > So to get the real size of the installed packages on a particular > filesystem, you need to get the troves, with files (but without > file contents), only single-count hardlink groups, and then use > an algorithm that takes into account particular filesystem features. > (Then, depending on your goals, you might want to add some room for > the Conary database, and then some more fudge for conary rollbacks.) > This is rather expensive processing compared to looking up a value > that is just the sum of the sizes of the files.
i think the current info is already sufficient to help find the low hanging fruits which will help bring down the size of the install. your details however explain why in the end the efforts will produce less reduction than it would seem from the current numbers. so that is helpful. greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix services: debugging, programming, training, linux sysadmin, web development -- pike programmer working in china community.gotpike.org foresight developer (open-steam|caudium).org foresightlinux.org unix sysadmin iaeste.at realss.com Martin Bähr http://www.iaeste.at/~mbaehr/ is.schon.org _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
