| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Steen Eugen Poulsen wrote: |
| 5 |
> Alistair Bush skrev: |
| 6 |
>> * It is used by many different packages. |
| 7 |
> |
| 8 |
> yes, this is the rubber rule. It pretty much allows any use flag to be |
| 9 |
> promoted to global when it has XX packages with it, the confusion comes |
| 10 |
> because the number of package using a flag is no indication whatever you |
| 11 |
> should set the flag globally or pr. package. |
| 12 |
|
| 13 |
Right, the only indication is if you want the functionality of the flag |
| 14 |
globally or per package :) |
| 15 |
|
| 16 |
> Seem to me that the word global is used in the portage tree to mean one |
| 17 |
> thing and then when we edit make.conf and /etc/portage we get another |
| 18 |
> global/local meaning. |
| 19 |
|
| 20 |
That's right. Global/local use flag descriptions have no relation to |
| 21 |
global/local setting via make.conf/package.use. As a non-dev you might |
| 22 |
just ignore the first classification. |
| 23 |
|
| 24 |
>>> I'm trying to write a Replicator for /etc/portage and that leads me to |
| 25 |
>>> work with USE flags, trying to design the replication of them among |
| 26 |
>>> similar systems, but I can't find the golden set of rules for how best |
| 27 |
>>> to apply USE flags. |
| 28 |
>>> |
| 29 |
>>> There seem to be a global/local USE flag system, but many so called |
| 30 |
>>> global flags has duplicated description marking them as local flags, or |
| 31 |
>>> they enable unneeded optional support. |
| 32 |
>> |
| 33 |
>> Unneeded by whom? |
| 34 |
> |
| 35 |
> The package in order for it to work. You don't need Java, Python, Perl, |
| 36 |
> Lua, whatever scripting support in most packages. For most of the ones |
| 37 |
> I've seen, I have to go write a Java/Python/Perl/Lua program, before I |
| 38 |
> actually need it. |
| 39 |
|
| 40 |
Well then don't enable those flags globally (that they are "global" |
| 41 |
doesn't mean you have to), enable them only for packages which have |
| 42 |
depending packages requiring them. Which you currently find out only by |
| 43 |
errors (graceful die messages, except bugs like the one you mentioned :) |
| 44 |
until there are finally use deps. |
| 45 |
|
| 46 |
> The words is given different meaning depending on whatever I'm looking |
| 47 |
> at the portage tree or working on configuring emerge. The portage trees |
| 48 |
> global flag, is no indication whatever I should put the flag in USE="" |
| 49 |
> in make.conf, in many cases a portage tree global flag is more an |
| 50 |
> indication that I should use it locally pr. package. |
| 51 |
|
| 52 |
Right, as mentioned above, there is no relation, although the |
| 53 |
"global/local" notion may suggest it. One might even ask why we have |
| 54 |
separate use.desc and use.local.desc then. Good question :) IMHO it's |
| 55 |
mostly administrative thing so people don't add many new global flags |
| 56 |
without consultation, but still can quickly add local flags just for |
| 57 |
their package. |
| 58 |
|
| 59 |
- -- |
| 60 |
Vlastimil Babka (Caster) |
| 61 |
Gentoo/Java |
| 62 |
-----BEGIN PGP SIGNATURE----- |
| 63 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 64 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 65 |
|
| 66 |
iD8DBQFG42AktbrAj05h3oQRAkfjAJ4zdWFWzLAswbDTq/hvszouoI1gYgCfV/j4 |
| 67 |
w0aFRUzi5RbOJMAs9M7O3no= |
| 68 |
=7Y8j |
| 69 |
-----END PGP SIGNATURE----- |
| 70 |
-- |
| 71 |
gentoo-dev@g.o mailing list |
Archives