1 |
On Tuesday 27 September 2005 11:23, Jason Stubbs wrote: |
2 |
> So what needs to be done to fix it? Well, what is the purpose of |
3 |
> USE_EXPAND? Put simply, it is to allow the user to select one or more |
4 |
> features of a package from a list of choices. How is this different to USE |
5 |
> flags? The choices all pertain to one aspect of the package(s). |
6 |
The way ELIBC, KERNEL, USERLAND are used, is instead something different. They |
7 |
don't allow users to select what they want, they allow profiles to declare |
8 |
what they are created for. |
9 |
If some user changes one of these variables, he's *really* screwed up, as they |
10 |
change quite a few things in the ebuilds (for example, if kernel is not |
11 |
linux, kdelibs doesn't build support for dnotify, gamin for inotify, and a |
12 |
few more options in the way). |
13 |
|
14 |
I think at least these three variables should be hidden from users, as they |
15 |
should not mean anything to them. |
16 |
In alternative, there was the proposal of a use.force file, that would allow |
17 |
to force some flags on and use that instead of the use-expanded variables, |
18 |
but currently it doesn't seem to be created and the QA notice problem is |
19 |
still not solved, those flags should be forced by some profiles and masked by |
20 |
others, as they are not intended to be changed by users. |
21 |
|
22 |
-- |
23 |
Diego "Flameeyes" Pettenò |
24 |
Gentoo Developer - http://dev.gentoo.org/~flameeyes/ |
25 |
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM) |