From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] use.force support
Date: Mon, 13 Jun 2005 18:12:01 -0400 [thread overview]
Message-ID: <200506131812.01312.vapier@gentoo.org> (raw)
In-Reply-To: <200506132327.08662@enterprise.flameeyes.is-a-geek.org>
On Monday 13 June 2005 05:27 pm, Diego 'Flameeyes' Pettenò wrote:
> On Monday 13 June 2005 23:08, Alec Warner wrote:
> > How is this not just a consequence of USE="-*"...that is what this does;
> > turns off ALL use flags. How is use.force ( or the concept thereof )
> > not breaking the 'easy' interpretation of USE="-*" because now things
> > aren't -*, they are -* + use.force things.
>
> It's exactly what we want to avoid, -* everything can breaks things for
> useflags like uclibc (now replaced by elibc_uclibc) and hardened and so on
> which needs to be enabled *everytime*.
and is the EXACT reason we have the 'nocxx' USE flag instead of 'cxx' ... if
we put 'USE=cxx' into profiles' make.defaults, people who have USE=-* will
get a broken gcc
and no matter how much i'd like to close bugs generated in that case with "NOT
MY FAULT YOU HAVE A STUPID CONFIGURATION FILE YOU TOOL", i feel like that
would probably not be too friendly
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-06-13 22:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 14:40 [gentoo-dev] use.force support Sven Wegener
2005-06-13 16:47 ` Harald van Dijk
2005-06-13 18:23 ` Sven Wegener
2005-06-14 5:42 ` Harald van Dijk
2005-06-13 18:28 ` Simon Stelling
2005-06-13 19:56 ` Dan Meltzer
2005-06-13 20:40 ` Kito
2005-06-13 20:54 ` Sven Wegener
2005-06-14 22:34 ` Sami Näätänen
2005-06-13 22:43 ` Sven Wegener
2005-06-14 2:17 ` Kumba
2005-06-13 20:50 ` Sven Wegener
2005-06-13 21:08 ` Alec Warner
2005-06-13 21:27 ` Diego 'Flameeyes' Pettenò
2005-06-13 22:12 ` Mike Frysinger [this message]
2005-06-14 14:02 ` Jan Kundrát
2005-06-13 21:38 ` Sven Wegener
2005-06-14 17:46 ` Alec Warner
2005-06-14 17:54 ` Diego 'Flameeyes' Pettenò
2005-06-15 1:16 ` Sven Wegener
2005-06-13 22:56 ` Ned Ludd
2005-06-13 23:29 ` Mike Frysinger
2005-06-15 1:26 ` Sven Wegener
2005-06-15 2:50 ` Donnie Berkholz
2005-06-15 9:03 ` [gentoo-dev] " Duncan
2005-06-15 23:17 ` Georgi Georgiev
2005-06-16 6:04 ` [gentoo-dev] " Duncan
2005-06-15 11:43 ` [gentoo-dev] " Sven Wegener
2005-06-20 0:32 ` Jason Stubbs
2005-06-15 13:52 ` Chris Gianelloni
2005-06-14 2:43 ` Jason Wever
2005-06-14 9:21 ` Diego 'Flameeyes' Pettenò
2005-06-16 13:30 ` Herbie Hopkins
2005-06-15 10:16 ` Thomas de Grenier de Latour
2005-06-15 11:53 ` Sven Wegener
2005-06-15 13:51 ` Alec Warner
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=200506131812.01312.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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