public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@lycos.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: package dependencies
Date: Thu, 16 Feb 2006 22:10:50 +0000	[thread overview]
Message-ID: <dt2t7k$e75$1@sea.gmane.org> (raw)
In-Reply-To: 342e1090602161140q1d0c909aqa6aa7c9510308c1c@mail.gmail.com

Daniel da Veiga wrote:

> On 2/16/06, Nick Smith <nick.smith79@gmail.com> wrote:
>> On 2/16/06, Ghaith Hachem <blacksadness@gmail.com> wrote:
>> > usualy portatge tells you what is blocking what
>> > anyway try emerge -av it will give you an idea of what you need
>> >
>> right, but i want to know that the package im going to remove because
>> its blocking something else isnt needed by another package on my
>> system that has nothing to do with the package im trying to emerge.
>> can that be done?  am i making any sense?

Usually unmerging the blocker and re-emerging later on fixes it.  Sometimes
there may be a cyclical blocking scenario whereby the two packages (or
their dependencies) are categorically incompatible.  I don't believe
there's an easy solution for such a predicament.  In your case I would try
to unmerge the blocker, emerge what you want, re-emerge the original
blocker.  If portage let's you do it then that's that.  :)
-- 
Regards,
Mick

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-16 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 18:59 [gentoo-user] package dependencies Nick Smith
2006-02-16 19:13 ` Ghaith Hachem
2006-02-16 19:33   ` Nick Smith
2006-02-16 19:40     ` Daniel da Veiga
2006-02-16 22:10       ` Mick [this message]
2006-02-16 19:13 ` gentuxx
2006-02-16 22:46 ` [gentoo-user] " Catalin Trifu
2006-02-20  7:33   ` Catalin Grigoroscuta

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='dt2t7k$e75$1@sea.gmane.org' \
    --to=michaelkintzios@lycos.co.uk \
    --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