From: Daniel <danny@ilievnet.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] world favorites: pros and cons
Date: Wed, 05 Jul 2006 14:11:44 +0300 [thread overview]
Message-ID: <44AB9E70.6010205@ilievnet.com> (raw)
In-Reply-To: <20060705115509.2905ae6d@hactar.digimed.co.uk>
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
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-05 11:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 9:48 [gentoo-user] world favorites: pros and cons Daniel
2006-07-05 10:10 ` Neil Bothwick
2006-07-05 10:21 ` Alexander Skwar
2006-07-05 10:18 ` Alexander Skwar
2006-07-05 10:55 ` Neil Bothwick
2006-07-05 11:11 ` Daniel [this message]
2006-07-05 11:33 ` Rumen Yotov
2006-07-05 11:54 ` Daniel Iliev
2006-07-05 12:14 ` Neil Bothwick
2006-07-05 12:43 ` Daniel Iliev
2006-07-05 13:16 ` Alexander Skwar
2006-07-05 14:47 ` Alan McKinnon
2006-07-05 13:21 ` Neil Bothwick
2006-07-05 14:29 ` Daniel Iliev
2006-07-05 15:08 ` Neil Bothwick
2006-07-05 16:53 ` Daniel Iliev
2006-07-05 20:15 ` Neil Bothwick
2006-07-05 16:38 ` Richard Fish
2006-07-05 17:10 ` Daniel Iliev
2006-07-05 18:15 ` Richard Fish
2006-07-05 18:59 ` Daniel Iliev
2006-07-05 19:47 ` Richard Fish
2006-07-05 16:54 ` Daniel da Veiga
2006-07-05 18:30 ` Daniel Iliev
2006-07-05 19:17 ` Daniel da Veiga
2006-07-05 20:01 ` Daniel Iliev
2006-07-28 18:30 ` Enrico Weigelt
2006-07-28 18:46 ` [gentoo-user] " Jim Ramsay
2006-07-28 18:57 ` Alexander Skwar
2006-07-28 19:10 ` Enrico Weigelt
2006-07-28 19:30 ` Jim Ramsay
2006-07-28 20:39 ` Daniel da Veiga
2006-07-28 21:03 ` Jim Ramsay
2006-07-28 21:03 ` Jim Ramsay
2006-08-07 16:53 ` Enrico Weigelt
2006-07-05 22:27 ` [gentoo-user] " Daniel Iliev
2006-07-05 22:43 ` Ryan Tandy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44AB9E70.6010205@ilievnet.com \
--to=danny@ilievnet.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox