From: Daniel Pielmeier <billie@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage getting mixed up with USE?
Date: Wed, 22 Jun 2011 12:48:07 +0200 [thread overview]
Message-ID: <BANLkTimkPRrOePuJHqiDqngVSELPAVFbYg@mail.gmail.com> (raw)
In-Reply-To: <20110622104754.6a51d1eb@zaphod.digimed.co.uk>
2011/6/22 Neil Bothwick <neil@digimed.co.uk>:
> On Wed, 22 Jun 2011 10:18:05 +0200, Alan McKinnon wrote:
>
>> The following USE changes are necessary to proceed:
>> #required by www-client/dillo-2.2, required by mail-client/claws-
>> mail-3.7.9-r1[dillo], required by claws-mail (argument)
>> >=x11-libs/fltk-2.0_pre6970-r1 -cairo
>
>> Any reason why portage is telling me to set a USE that is already
>> there per portage's own output?
>
> As Daniel said, this is what portage needs, it's been that way since the
> autounmask stuff was introduced. Or you could emerge Claws with -dillo
> and use the fancy plugin for HTML rendering. I stopped using the dillo
> renderer years ago.
Actually it is like that since the introduction of use-dependencies
like cat/pkg-ver[use] and _before_. Autounmask ist just for the users
convenience to copy paste the needed changes to package.use. I guess
the reason for this coming up more often is that develpopers start to
use use-dependencies more often.
Before the introduction of use dependencies the only possible way was
to stop emerge at build time and tell the user he needs USE="X" for
package Y. With use dependencies it is now possible to inform the user
about it when resolving the dependencies.
So nothing has changed. If a package requires use settings which are
different from the defaults you have to override this on a per package
basis via package.use.
--
Regards,
Daniel
next prev parent reply other threads:[~2011-06-22 10:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 8:18 [gentoo-user] portage getting mixed up with USE? Alan McKinnon
2011-06-22 8:49 ` Daniel Pielmeier
2011-06-22 9:15 ` Alan McKinnon
2011-06-22 9:31 ` Daniel Pielmeier
2011-06-22 9:50 ` Alan McKinnon
2011-06-22 9:47 ` Neil Bothwick
2011-06-22 9:53 ` Alan McKinnon
2011-06-22 10:43 ` Neil Bothwick
2011-06-22 11:54 ` Alan McKinnon
2011-06-22 12:22 ` Daniel Pielmeier
2011-06-22 12:41 ` Alan McKinnon
2011-06-22 14:19 ` Mick
2011-06-22 14:44 ` Neil Bothwick
2011-06-22 15:31 ` Alan McKinnon
2011-06-22 16:05 ` Mick
2011-06-22 16:22 ` Neil Bothwick
2011-06-22 16:30 ` Sebastian Beßler
2011-06-22 16:59 ` Alan McKinnon
2011-06-23 11:31 ` Daniel Pielmeier
2011-06-23 19:40 ` Alan McKinnon
2011-06-22 17:11 ` Sebastian Beßler
2011-06-22 18:22 ` Dale
2011-06-22 19:16 ` Sebastian Beßler
2011-06-22 20:12 ` Alan McKinnon
2011-06-22 22:35 ` Mick
2011-06-22 22:58 ` Neil Bothwick
2011-06-23 1:35 ` Matthew Finkel
2011-06-23 6:59 ` Sebastian Beßler
2011-06-23 19:38 ` Alan McKinnon
2011-06-23 22:06 ` Neil Bothwick
2011-06-23 22:31 ` Alan McKinnon
2011-06-23 22:56 ` Mike Edenfield
2011-06-24 0:05 ` Neil Bothwick
2011-06-24 0:10 ` Neil Bothwick
2011-06-24 8:00 ` Sebastian Beßler
2011-06-23 20:05 ` Yohan Pereira
2011-06-24 8:11 ` Sebastian Beßler
2011-06-22 10:48 ` Daniel Pielmeier [this message]
2011-06-22 11:57 ` Alan McKinnon
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=BANLkTimkPRrOePuJHqiDqngVSELPAVFbYg@mail.gmail.com \
--to=billie@gentoo.org \
--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