Daniel wrote:
Neil Bothwick wrote:
On Wed, 05 Jul 2006 12:18:20 +0200, Alexander Skwar wrote:
But you'll still miss some packages this way - packages which aren't
in the world file and which are also no dependency of *CURRENTLY*
installed packages. Those are normally packages, which aren't used
anymore and could be removed. I forgot how to find out, which packages
that are.
emerge --depclean --pretend
Your replies make me feel I haven't done wrong trying to put every
single package in the world set. Actually in my fear not to miss some
updates I use this script:
---
emerge -DuNpv <package-name> | cut -sf2 -d '/' |\
cut -f1 -d ' '|\
while read pkg;
do find /usr/portage/ -name ${pkg}.ebuild;
done | sed 's/\/usr\/portage\///g' |\
while read a;
do echo ${a%/*}; done |\
xargs -n1 emerge
---
This way all dependencies get individually emerged and therefore
recorded in the world file. Of course excluding some particular cases.
For example:
"emerge xmms" -> pulls-in gtk+-1.2", while
"emerge mozilla-firefox" -> pulls-in gtk+2.8.
So in this case the aforementioned script used with "emerge xmms
mozilla-firefox" will individually emerge only gtk+-2.8 and gtk+-1.2
would be emerged as dependency of xmms and won't get recorded in the
world set.
--
Best regards
Daniel
Hi,
In the contrary, i (at least) put in 'world' only things i emerge.
The reason - the world-file is smaller and eventually is scanned more
quickly.
Unless you also use "-D|--deep" option, which also scans the deps.
HTH.Rumen
--
[email protected] mailing list
