1 |
On Thu, 10 Feb 2011, Ryan Hill wrote: |
2 |
|
3 |
> On Wed, 9 Feb 2011 13:04:11 +0100 |
4 |
> Ulrich Mueller <ulm@g.o> wrote: |
5 |
> |
6 |
>> Maybe we also need a guideline that whenever possible, ebuilds should |
7 |
>> accept the default USE flags from our profiles as a valid combination? |
8 |
>> Or, in the exceptional case when that isn't possible, a package.use |
9 |
>> entry should be added to profiles. |
10 |
> |
11 |
> Yes, we need to be careful when using REQUIRED_USE with global USE flags, |
12 |
> especially the defaults. If a new user has to spend half an hour trying to |
13 |
> figure out the magic combination of USE flags that will allow them to run |
14 |
> `emerge @world` on their fresh install they're going to get frustrated and |
15 |
> leave. |
16 |
> |
17 |
> I imagine it would break stage building as well (?) |
18 |
|
19 |
The stage building process is affected by ebuilds that die for |
20 |
conflicting and or missing use flags. Fortunately, stage building only |
21 |
builds packages in the system set and not the world set. |
22 |
So if you have a package in the system set, before you make it die in the |
23 |
above scenario, be sure to check with releng the impact and try to provide |
24 |
an "exception" for USE="build". |
25 |
|
26 |
--- |
27 |
Regards, |
28 |
|
29 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
30 |
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng |