From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] unstable glib pulled down, but why?
Date: Mon, 30 Jun 2008 19:06:00 +0200 [thread overview]
Message-ID: <200806301906.00437.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <93ae19410806301102q578702d5y6d1739b27f0ee4b4@mail.gmail.com>
On Monday 30 June 2008, brullo nulla wrote:
> > Seems a reasonable question, but will be almost impossible to
> > implement, as how would you define a package that can "be happily
> > merged independently" of a blocking package?
> >
> > portage is software, it isn't intelligent so it doesn't know how to
> > answer that. I admit it's annoying though.
>
> The block will in many cases affect only a branch of the dependency
> tree. For example, in this case it is all blocked because glibmm
> wants a masked glib. Portage knows that glibmm wants the masked glib,
> so it knows that glibmm causes the trouble. So it could in principle
> give me what is to update except for glibmm and glib - and give me
> the error about those two.
>
> Am I missing something?
Probably not :-)
But the portage code has been described as difficult to maintain, so I
suppose the correct person to ask is Zac himself. Perhaps there are
tricky edge cases?
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-30 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 18:39 [gentoo-user] unstable glib pulled down, but why? b.n.
2008-06-29 18:51 ` Neil Bothwick
2008-06-29 20:45 ` b.n.
2008-06-29 21:24 ` Daniel Iliev
2008-06-29 21:36 ` Neil Bothwick
2008-06-29 22:04 ` b.n.
2008-06-29 23:13 ` Neil Bothwick
2008-06-29 23:56 ` b.n.
2008-06-30 15:57 ` Alan McKinnon
2008-06-30 18:02 ` brullo nulla
2008-06-30 17:06 ` Alan McKinnon [this message]
2008-06-30 20:57 ` b.n.
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=200806301906.00437.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.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