1 |
Sven Wegener wrote: |
2 |
> On Mon, Jun 13, 2005 at 05:08:09PM -0400, Alec Warner wrote: |
3 |
> |
4 |
>>Sven Wegener wrote: |
5 |
>> |
6 |
>> |
7 |
>>>use.force might not be the best name, but it's what we do with it for |
8 |
>>>most of our users. Being able to -flag in /etc/portage/profile/use.force |
9 |
>>>is just because /etc/portage/profile gets added to the cascaded profile |
10 |
>>>chain. Everything we add to portage that allows a profile to revert |
11 |
>>>some behaviour added by parent profiles, can also be done with |
12 |
>>>/etc/portage/profile and it's good that way. So, that we're able to |
13 |
>>>-flag in use.force is just part of the way cascaded profiles work. It's |
14 |
>>>not a feature that will be added just to support use.force. Primary |
15 |
>>>reason for use.force is to have a way to activate flags even if USE="-*" |
16 |
>>>is in make.conf or environment. |
17 |
>> |
18 |
>>How is this not just a consequence of USE="-*"...that is what this does; |
19 |
>>turns off ALL use flags. How is use.force ( or the concept thereof ) |
20 |
>>not breaking the 'easy' interpretation of USE="-*" because now things |
21 |
>>aren't -*, they are -* + use.force things. |
22 |
>> |
23 |
>>It's one of those "if you use USE="-*" you should know the consequences |
24 |
>>of it...kind of deals. |
25 |
> |
26 |
> |
27 |
> There are some USE flags that must survive the -* thing and already do |
28 |
> it. One of them being ARCH, which is always there. And the USE_EXPANDed |
29 |
> ones, the current important being being userland_*, kernel_* and elibc_* |
30 |
> which are needed for special dependencies and checks. They are not to be |
31 |
> modified by users by using USE in make.conf or the environment. They |
32 |
> depend on the chosen profile and should always be enabled. We're not |
33 |
> talking about every day USE flags, but really special USE flags, like |
34 |
> multilib, selinux or the USE_EXPANDed ones that *must* be turned on for |
35 |
> the chosen profile. Don't think of them like every day USE flags that |
36 |
> allow you to tweak your system, they are used to pass some information |
37 |
> from profiles to the ebuilds in a way portage can easily handle it. |
38 |
> |
39 |
> Hm, use.must sounds bad once I think about it more. |
40 |
> |
41 |
> Sven |
42 |
> |
43 |
I'm probably a little behind here, since this has been used for a while, |
44 |
but I guess more discussion and ideas are good. |
45 |
|
46 |
It seems like this is an abuse of USE flags, somewhat. I guess programs |
47 |
could have support for elibc_X or elibc_Y or userland_GNU or |
48 |
userland_DARWIN/BSD but why a USE flag for these? If they must be |
49 |
forced, force them in the environment outside of USE flag usage. USE |
50 |
flags are for turning off optional support for programs, that is their |
51 |
overall purpose. There isn't a use flag for kernel version, there is a |
52 |
function for that. Why is there not a function to determine |
53 |
userland/arch/libc? |
54 |
|
55 |
In this case I think this use.force deal will create more complexity in |
56 |
the USE flag area than help. This is not what use flags are for ( also |
57 |
for multilib and SELINUX ). |
58 |
-- |
59 |
gentoo-dev@g.o mailing list |