1 |
Seems like use.force might be a bad name..... when I first read the |
2 |
email, and saw use.force, the first thing that came to mind was |
3 |
"gentoo forcing something?" and even after reading the email, I |
4 |
wouldn't expect to be able to override something that was "forced." |
5 |
I'm not sure what a better name would be, but I think there may be |
6 |
one... |
7 |
|
8 |
also, wouldn't the override be in use.unforce? >_< |
9 |
|
10 |
On 6/13/05, Simon Stelling <blubb@g.o> wrote: |
11 |
> Sven Wegener wrote: |
12 |
> > We just had a short discussion over in #gentoo-portage and the idea of |
13 |
> > an use.force file for profiles came up. It allows us to force some USE |
14 |
> > flags to be turned on for a profile. It's not possible to disable this |
15 |
> > flag by make.conf, the environment or package.use. But we would not be |
16 |
> > Gentoo, if we don't leave a backdoor. You can disable the flag by |
17 |
> > putting -flag in /etc/portage/profile/use.force if you really need to. |
18 |
> > Same goes for sub-profiles that need to disable this flag. |
19 |
> |
20 |
> Yay! |
21 |
> |
22 |
> > I gues use.force has some other places where it is useful. Like the |
23 |
> > default-darwin profiles which use ARCH="ppc" and USE="ppc-macos" but the |
24 |
> > ppc-macos flag can be removed by using USE="-ppc-macos" in the |
25 |
> > environment. Or selinux profiles, to force the selinux flag to be turned |
26 |
> > on. |
27 |
> |
28 |
> It'll be also very useful for the amd64 profiles as in 2005.0 the use |
29 |
> flag 'multilib' is disabled but multilib-support is forced. (There are |
30 |
> no-multilib-profiles though.) |
31 |
> |
32 |
> > Comments? |
33 |
> |
34 |
> I consider use.force very useful, it'll finally make all the amd64 users |
35 |
> stop asking themselves why the documenation says they will get multilib |
36 |
> but the use flag is disabled, so please, go ahead implementing it. |
37 |
> |
38 |
> Regards, |
39 |
> |
40 |
> blubb |
41 |
> |
42 |
> -- |
43 |
> Simon Stelling |
44 |
> Gentoo/AMD64 Operational Co-Lead |
45 |
> blubb@g.o |
46 |
> -- |
47 |
> gentoo-dev@g.o mailing list |
48 |
> |
49 |
> |
50 |
|
51 |
-- |
52 |
gentoo-dev@g.o mailing list |