From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Neil Bothwick <neil@digimed.co.uk>
Subject: Re: [gentoo-user] portage getting mixed up with USE?
Date: Wed, 22 Jun 2011 11:53:19 +0200 [thread overview]
Message-ID: <2722186.Lc5eY5q7TY@nazgul> (raw)
In-Reply-To: <20110622104754.6a51d1eb@zaphod.digimed.co.uk>
On Wednesday 22 June 2011 10:47:54 Neil Bothwick did opine thusly:
> 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.
In other words, we must now all end up with giganticly bloated
package.use files to satisfy every "built with use" requirement
system-wide? What's wrong with looking at the defaults and saying
"Gee, you know what, the implicit rules on the box are going to do the
right thing anyway, so let's proceed and build the stuff?"
> Or you could emerge Claws with
> -dillo and use the fancy plugin for HTML rendering. I stopped using
> the dillo renderer years ago.
Well, that's an option.
But I fear this behaviour is going to rear it's head many more times
with other ebuilds.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-06-22 9:55 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 [this message]
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=2722186.Lc5eY5q7TY@nazgul \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=neil@digimed.co.uk \
/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