1 |
On Wednesday 15 June 2005 20:43, Sven Wegener wrote: |
2 |
> On Tue, Jun 14, 2005 at 07:50:13PM -0700, Donnie Berkholz wrote: |
3 |
> > Sven Wegener wrote: |
4 |
> > > On Mon, Jun 13, 2005 at 06:56:43PM -0400, Ned Ludd wrote: |
5 |
> > > >I'm in favor of this. Would you mind calling it package.autouse, |
6 |
> > > >package.use.auto or are you set on .force? |
7 |
> > > |
8 |
> > > As Mike already wrote those names are too confusing with the automatic |
9 |
> > > activated USE flags. We already had some suggestions in this thread, |
10 |
> > > but none of them actually matched the purpose of the file. At least in |
11 |
> > > my opinion. use.force matches it best, but the "force" part is a quite |
12 |
> > > hard term. How about use.profile? Because these USE flags are activated |
13 |
> > > or needed by the profile. |
14 |
> > |
15 |
> > How about use.required, since they're required by the profile? |
16 |
> |
17 |
> Sounds good to me. use.required sounds softer than use.force but still |
18 |
> has this "touch me and things may break horribly" bit. |
19 |
|
20 |
So use.required it is then. To recap, use.required forces USE flags to be set |
21 |
and can only be overridden in a sub-profile. Transition from the current |
22 |
USE_EXPAND method is by simply copying the relevant USE flags to the new |
23 |
use.required file. |
24 |
|
25 |
Currently missing from the USE_EXPAND method but what also needs to be done is |
26 |
to add the alternative system USE flags to use.mask. Also, this still hasn't |
27 |
addressed the QA notices output during merges. For this, I'll add support for |
28 |
${PORTDIR}/profiles/use.internal which will list USE flags which can be used |
29 |
anywhere without having to be specified in IUSE; that is, they can be used |
30 |
with useq, SRC_URI and *DEPEND. |
31 |
|
32 |
Note, use.internal doesn't and shouldn't cover the normal USE_EXPAND flags. |
33 |
I'll cover those shortly in another post. |
34 |
|
35 |
Regards, |
36 |
Jason Stubbs |