public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 11:31:09 +0200	[thread overview]
Message-ID: <BANLkTinqNoZMO7Rz2hgGDXLAUiKSuRUBGQ@mail.gmail.com> (raw)
In-Reply-To: <5886949.K0a64kT5Su@nazgul>

2011/6/22 Alan McKinnon <alan.mckinnon@gmail.com>:
> On Wednesday 22 June 2011 10:49:04 Daniel Pielmeier did opine thusly:
>>
>> I guess it displays the USE settings how they should be and
>> afterwards prints the required changes. Or does it build fltk with
>> USE="-cairo" if you just type emerge -av fltk?
>
> emerge -av fltk
>
> gives exactly the same output as above. The dillo ebuild doesn't seem
> to be causing this change in behaviour:
>
> RDEPEND="x11-libs/fltk:2[-cairo,jpeg=,png=]
>
> What it looks like is portage is insisting the package.use explicitly
> states the USE flags needed. This is wrong and I am not about to bloat
> package.use to cater for every "built with use" occurrence. Or perhaps
> it's now only looking at installed deps and not it's own dep graph
> when emerge runs.
>
> Portage should only care about whether the package is already built
> with use, or will be according to the dep graph

So you get the same recommendation about the use flag change?

If you have USE="cairo" in make.conf or it is enabled via some profile
(desktop?) you have to add >=x11-libs/fltk-2.0_pre6970-r1 -cairo to
package.use to override this on a per package basis. I think there is
no way around this.

-- 
Regards,
Daniel



  reply	other threads:[~2011-06-22  9:32 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 [this message]
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
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=BANLkTinqNoZMO7Rz2hgGDXLAUiKSuRUBGQ@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