public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --depclean wants to remove required packages
Date: Tue, 27 Feb 2007 17:45:17 +0100	[thread overview]
Message-ID: <200702271745.21439.bo.andresen@zlin.dk> (raw)
In-Reply-To: <200702271747.16022.alan@linuxholdings.co.za>

[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]

On Tuesday 27 February 2007 16:47:15 Alan McKinnon wrote:
> > > You have a bunch of packages that --depclean wants to remove. It
> > > looks like they should not be removed.
> >
> > A bit curious how you've reached that conclusion? Why shouldn't they?
>
> The OP said in his original mail
>
> "when I run emerge
> --depclean wants remove packages that would break dependencies"
>
> Presumably he knows his system well enough to know that the packages in
> question are necessary.
>
> I probably worded my statement wrongly as well. As written it implies
> that --depclean erroneously wants to remove things that should remain
> according to information in the ebuilds. I should have said --depclean
> wants to remove things that the OP would prefer to remain.

There are at least three reasons why you cannot rely on `equery depends` to 
tell you if a dependency which `emerge --depclean` is going to remove is 
required or not.

1) USE conditionals. This is adressed in latest ~arch gentoolkit (0.2.3) which 
prints the conditional. You still have to check the conditional yourself.

2) "|| ( bar baz )" blocks. `equery depends bar` and `equery depends baz` will 
print foo as depending on them. portage and hence `emerge --depclean` only 
requires one of them to satisfy the dep.

3) If the ebuild exists in the tree and has been modified since it was 
installed `emerge --depclean` will use the modified ebuild from the tree. 
`equery depend` will use the ebuild that was installed in /var/db/pkg.

In most if not all cases when `emerge --depclean` and `equery depends` 
disagree the former is correct (as of portage-2.1.1 at least (or 2.1?)). If 
you want to verify it with the latter you need to investigate the ebuild to 
see if any of the mentioned three cases apply...

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-02-27 16:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25 17:50 [gentoo-user] emerge --depclean wants to remove required packages Mark Knecht
2007-02-25 18:19 ` Bo Ørsted Andresen
2007-02-25 20:51   ` Mark Knecht
2007-02-26 16:27     ` Mark Knecht
2007-02-26 16:46       ` Bo Ørsted Andresen
2007-02-26 17:49         ` Mark Knecht
2007-02-26 18:06           ` Bo Ørsted Andresen
2007-02-26 19:43 ` Alan McKinnon
2007-02-26 20:53   ` Bo Ørsted Andresen
2007-02-27 15:47     ` Alan McKinnon
2007-02-27 16:45       ` Bo Ørsted Andresen [this message]
2007-02-26 23:23   ` Mark Knecht
2007-02-27 16:02     ` Alan McKinnon
2007-02-27 23:22       ` Mark Knecht

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=200702271745.21439.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --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