| 1 |
Alistair Bush skrev: |
| 2 |
> * It is used by many different packages. |
| 3 |
|
| 4 |
yes, this is the rubber rule. It pretty much allows any use flag to be |
| 5 |
promoted to global when it has XX packages with it, the confusion comes |
| 6 |
because the number of package using a flag is no indication whatever you |
| 7 |
should set the flag globally or pr. package. |
| 8 |
|
| 9 |
Seem to me that the word global is used in the portage tree to mean one |
| 10 |
thing and then when we edit make.conf and /etc/portage we get another |
| 11 |
global/local meaning. |
| 12 |
|
| 13 |
> * It has a general non-specific purpose. |
| 14 |
|
| 15 |
Shouldn't that be "It has a general specific purpose". |
| 16 |
|
| 17 |
> The second point is important. If the effect of the thing USE flag upon |
| 18 |
> pkg-one is substantially different from the effect it has upon pkg-two, |
| 19 |
> then thing is not a suitable candidate for being made a global flag. In |
| 20 |
> particular, note that if client and server USE flags are ever |
| 21 |
> introduced, they can not be global USE flags for this reason. |
| 22 |
|
| 23 |
Again you seem to talk about specific purpose, but the quoted text say |
| 24 |
non-specific, excuse me for being confused. |
| 25 |
|
| 26 |
>> I'm trying to write a Replicator for /etc/portage and that leads me to |
| 27 |
>> work with USE flags, trying to design the replication of them among |
| 28 |
>> similar systems, but I can't find the golden set of rules for how best |
| 29 |
>> to apply USE flags. |
| 30 |
>> |
| 31 |
>> There seem to be a global/local USE flag system, but many so called |
| 32 |
>> global flags has duplicated description marking them as local flags, or |
| 33 |
>> they enable unneeded optional support. |
| 34 |
> |
| 35 |
> Unneeded by whom? |
| 36 |
|
| 37 |
The package in order for it to work. You don't need Java, Python, Perl, |
| 38 |
Lua, whatever scripting support in most packages. For most of the ones |
| 39 |
I've seen, I have to go write a Java/Python/Perl/Lua program, before I |
| 40 |
actually need it. |
| 41 |
|
| 42 |
> As for the duplicate local USE flags, They are most |
| 43 |
> probably redundant. |
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
> See above. Also note that you are not enabling support for pythonapi, |
| 48 |
> you are enabling support for python. Would you enable support for |
| 49 |
> linuxheaders when you are without a linux kernel. |
| 50 |
|
| 51 |
I don't understand what support for python is. |
| 52 |
|
| 53 |
> If that is the case, then I would suggest you search bugzilla and then |
| 54 |
> file a bug. |
| 55 |
|
| 56 |
Off course, but thats hardly the point of mentioning here, it was for |
| 57 |
bringing general attention to a ebuild mistake, that happens again and |
| 58 |
again. |
| 59 |
|
| 60 |
> See above. I can only assume that virtualbox doesn't need to have a |
| 61 |
> local alsa use flag. |
| 62 |
|
| 63 |
alsa: Adds support for media-labs/alsa-lib (Advanced Linux Sound |
| 64 |
Architecture) |
| 65 |
|
| 66 |
Local Flag: Enable support for ALSA instead of OSS |
| 67 |
(app-emulation/virtualbox) |
| 68 |
|
| 69 |
In box's case it's an "alsa not oss" flag, the global flag tend to be |
| 70 |
"also alsa", though I wont put my head on the block claiming it's always |
| 71 |
that meaning it has. |
| 72 |
|
| 73 |
>> As I see it, Gentoo's USE flag system is one of it's greatest strength, |
| 74 |
>> but at the moment seems like there is missing some overall design for |
| 75 |
>> how to implement USE flags, making it a lot harder to use USE flags, as |
| 76 |
>> there is no clear definition of global or local flags. |
| 77 |
|
| 78 |
The words is given different meaning depending on whatever I'm looking |
| 79 |
at the portage tree or working on configuring emerge. The portage trees |
| 80 |
global flag, is no indication whatever I should put the flag in USE="" |
| 81 |
in make.conf, in many cases a portage tree global flag is more an |
| 82 |
indication that I should use it locally pr. package. |
Archives