public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] iuse defaults example
Date: Sun, 15 Jul 2007 14:53:12 +0200	[thread overview]
Message-ID: <20070715145312.7a120ffe@eusebe> (raw)
In-Reply-To: <20070715135720.689a621b.genone@gentoo.org>

On 2007/07/15, Marius Mauch <genone@gentoo.org> wrote:

> On Sun, 15 Jul 2007 11:53:08 +0200
> Thomas de Grenier de Latour <degrenier@easyconnect.fr> wrote:
> 
> > My point is just that it doesn't work that well with the USE_ORDER
> > that have been chosen. Even keeping the "-* in make.conf" case
> > appart (obviously my opinion on how it should behave was not widely
> > shared, i can live with that), there is still a problem with -* in
> > make.defaults files: the day you switch from IUSE="nocxx" to
> > IUSE="+cxx", will you remember that, as a consequence, you have to
> > fix hardened/2.6/minimal profile? 
> 
> Well, it's just like any other renaming of USE flags in that regard.

But it shows that the "we shouldn't care about per-ebuild defaults in
profiles" argument doesn't really stand, which is unfortunate because
Mike is probaly right that it would have been a good thing.

> And while I can see why people would want IUSE defaults to have a
> higher priority than USE in make.defaults and/or make.conf, I suspect
> the vast majority of users would get completely lost in finding out
> where a flag was enabled/disabled (the current system is already
> confusing to a lot of people until they get a detailed explanation).

I don't think it's something which would be that hard to explain to
users.  All it takes is having "emerge -pv" to clearly shows that
something unusual is happening when a flag value is overidden by an
IUSE-default, for instance with an exclamation mark suffix, and to
document that in the man page, with the rest of the --verbose output:
     ! suffix = profile's global default value for this flag is
  overidden by an ebuild-specific setting.  You can still enable / 
  disable it in your own configuration (make.conf or package.use)
  if you really want to.
Maybe i am over-estimating the average user, but to me it doesn't sound
that complicated or obscure.

--
TGL.
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-07-15 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10  4:58 [gentoo-dev] iuse defaults example William Hubbs
2007-07-10  5:20 ` Mike Frysinger
2007-07-10  8:31   ` Petteri Räty
2007-07-10  9:04     ` Mike Frysinger
2007-07-10 16:12   ` Thilo Bangert
2007-07-10 19:44     ` Thomas de Grenier de Latour
2007-07-10 20:30       ` Mike Frysinger
2007-07-10 20:47         ` Thomas de Grenier de Latour
2007-07-10 21:32           ` Mike Frysinger
2007-07-15  9:53             ` Thomas de Grenier de Latour
2007-07-15 11:57               ` Marius Mauch
2007-07-15 12:53                 ` Thomas de Grenier de Latour [this message]
2007-07-15 19:22               ` Mike Frysinger
2007-07-15 20:24                 ` Arfrever Frehtes Taifersar Arahesis
2007-07-15 21:21                   ` Mike Frysinger
2007-07-16 11:42                 ` [gentoo-dev] " Steve Long

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=20070715145312.7a120ffe@eusebe \
    --to=degrenier@easyconnect.fr \
    --cc=gentoo-dev@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