From: Harm Geerts <harmgeerts@home.nl>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Re: Re: libungif and giflib conflict.
Date: Wed, 2 Nov 2005 22:59:51 +0100 [thread overview]
Message-ID: <200511022259.51970.harmgeerts@home.nl> (raw)
In-Reply-To: <pan.2005.11.02.20.54.23.514501@cox.net>
On Wednesday 02 November 2005 21:54, Duncan wrote:
> Hmm... That --noreplace is a new one on me. I normally simply
>
> echo <category/pkg> >> /var/lib/portage/world
>
> That appends the echoed cat/package to the end of the named file,
> accomplishing what we are after. The only down side to doing it manually
> (using echo) is if you typo. Still, that's not hard to catch and fix, if
> depclean still wants to remove the package you (thought you) just added.
> Newer versions of portage (don't believe it's in stable portage yet) even
> have an emaint command that removes the bad lines for you.
So did I, but now the warning `emerge depclean` produces tells me I can use
this. I find this rather nice as it is a lot safer and keeps the world file
free from user errors. For example replacing >> with > would be the most
destructive user error :P
I have portage 2.0.53_rc7 installed and I'm not sure which version introduced
--noreplace so it might not be available for everyone yet.
> 2. All this should reemphasize the role of the world file. It should
> list all your "leaf" packages, for the most part, executables. It should
> NOT list "trunk and branch" packages, dependencies of the leaves, for the
> most part, libraries and the like.
Ed Catmur has written a script that prunes the world file.
http://home.jesus.ox.ac.uk/~ecatmur/my-bin/dep
This will tune your world to only list leaf packages.
But this may not always be desired, use at your own discretion.
I've got nothing else to add so I guess this concludes the course "Maintaining
Gentoo in a nutshell" by Duncan and Harm Geerts :)
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-02 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 5:36 [gentoo-amd64] libungif and giflib conflict Nick Currier
2005-11-01 5:52 ` Barry.SCHWARTZ
2005-11-01 6:00 ` Brian Litzinger
2005-11-01 8:36 ` [gentoo-amd64] " Duncan
2005-11-01 15:07 ` Nick Currier
2005-11-01 17:39 ` Brian Litzinger
2005-11-01 18:19 ` [gentoo-amd64] " Duncan
2005-11-02 4:30 ` Nick Currier
2005-11-02 13:09 ` Harm Geerts
2005-11-02 19:42 ` Nick Currier
2005-11-02 20:54 ` [gentoo-amd64] " Duncan
2005-11-02 21:59 ` Harm Geerts [this message]
2005-11-02 23:07 ` [gentoo-amd64] " Duncan
2005-11-03 0:52 ` [gentoo-amd64] " Sebastian Redl
2005-11-03 2:32 ` Harm Geerts
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=200511022259.51970.harmgeerts@home.nl \
--to=harmgeerts@home.nl \
--cc=gentoo-amd64@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