| 1 |
On 11/17/2014 09:40 PM, William Hubbs wrote: |
| 2 |
> On Fri, Nov 14, 2014 at 11:42:57PM +0100, Alexander Hof wrote: |
| 3 |
>> Mike Gilbert wrote: |
| 4 |
>>>> There are people that don't want c++ and gcc:4.7 can still bootstrap |
| 5 |
>>>> without. |
| 6 |
>>>> |
| 7 |
>>> |
| 8 |
>>> Those people "know what they are doing" and could un-force the use |
| 9 |
>>> flag. That would prevent people from accidentally disabling it via |
| 10 |
>>> USE="-*". |
| 11 |
>> |
| 12 |
>> Are we talking about forcing +cxx globally or for gcc (+toolchain)? |
| 13 |
>> |
| 14 |
>> Has this been a major problem in the past? Shouldn't people who set |
| 15 |
>> USE="-*" also "know what they are doing"? |
| 16 |
> |
| 17 |
> This is my feeling as well. |
| 18 |
> |
| 19 |
> If someone using Gentoo uses USE="-* foo bar ..." they get to keep the |
| 20 |
> pieces. |
| 21 |
> |
| 22 |
> William |
| 23 |
> |
| 24 |
|
| 25 |
Using USE="-*" reveals so many random assumptions and untested ebuild |
| 26 |
configurations that we should definitely rethink that sentiment. |
| 27 |
|
| 28 |
And arch testers partly do exactly that. |
| 29 |
So I think it's an excuse for bad ebuild USE flags and dependencies. |
| 30 |
If your ebuild does not compile with USE="-*" (except because of |
| 31 |
REQUIRED_USE or pkg_setup bailing out), then you did something wrong. |
| 32 |
|
| 33 |
People already use this configuration and all related bug reports are valid. |
Archives