public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Harm Geerts <harmgeerts@home.nl>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Re: libungif and giflib conflict.
Date: Wed, 2 Nov 2005 14:09:38 +0100	[thread overview]
Message-ID: <200511021409.38666.harmgeerts@home.nl> (raw)
In-Reply-To: <3ab1ed150511012030w21b86b41ya6736a38d521e3aa@mail.gmail.com>

On Wednesday 02 November 2005 05:30, Nick Currier wrote:
> Looks like that got it guys. Thanks tons for the help.... It seems I broke
> portage by running only part ~amd64 packages. revdep-rebuild found it but
> it took twice to fix..... depclean wants to get rid of tons of stuff though
> so I'm thinking this is a bad idea or I have bigger problems.... Kudos to
> AMD64 Gentoo for the best support team in open source.

It's normal for a system that hasn't been maintained the way it should ;)
1. Look over the list of packages that would be unmerged with:
# emerge --pretend depclean
2. Inject the packages that should not be removed in your world file with:
# emerge --noreplace <package name>

Repeats steps 1 and 2 untill you are satisfied.
3. clean the remaining packages with:
# emerge --ask depclean
4. rebuild packages that were built against older/removed libaries:
# revdep-rebuild --pretend (part of app-portage/gentoolkit)

In order to keep your system clean in the future upgrade world like this:
1. upgrade your world, remerge packages that have a changed USE flag and 
upgrade deep dependencies.
# emerge --ask --deep --newuse --upgrade world
2. rebuild packages that were built against older/removed libaries
# revdep-rebuild --pretend

If you ever remove a package do it like this:
1. remove the package
# emerge --ask --unmerge package
2. remove the dependencies but always check the output. other packages might 
use them even though they are not a direct dependency
# emerge --ask depclean
3. rebuild packages that were build against libaries you just removed
# revdep-rebuild --pretend

This is how I maintain all my systems.
If anyone has remarks/tips I'd be glad to hear them.
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-11-02 13:12 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 [this message]
2005-11-02 19:42               ` Nick Currier
2005-11-02 20:54               ` [gentoo-amd64] " Duncan
2005-11-02 21:59                 ` Harm Geerts
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=200511021409.38666.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