| 1 |
Brian Harring posted on Sat, 17 Dec 2011 12:12:45 -0800 as excerpted: |
| 2 |
|
| 3 |
> On Sat, Dec 17, 2011 at 11:24:37AM +0100, Pacho Ramos wrote: |
| 4 |
>> I am referring in this case to abiword, it has a "plugins" USE flag |
| 5 |
>> that enables some minimal set of plugins and, then, a lot of USE flags |
| 6 |
>> for building extra plugins (with extra dependencies). All of this extra |
| 7 |
>> plugins need "plugins" USE flag to be enabled. Is there any way to |
| 8 |
>> write a REQUIRED_USE flag variable without needing to list all USE |
| 9 |
>> flags depending on "plugins" to be set? |
| 10 |
> |
| 11 |
> I think the better question is why you have a plugin use flag if the |
| 12 |
> vast majority of interesting flags require it. |
| 13 |
> |
| 14 |
> What's the gain of having plugin controllable, vs forced on by default |
| 15 |
> (or force on by one of the flags you referenced being enabled)? |
| 16 |
|
| 17 |
Indeed, that /is/ a good question. =:^) |
| 18 |
|
| 19 |
What about adding USE=minimal to turn off plugins entirely, thus making |
| 20 |
the default if it's not turned on the basic plugins? |
| 21 |
|
| 22 |
That would kill the complicated dependencies for the individual plugin |
| 23 |
flags and with a package specific description for USE=minimal that says |
| 24 |
it builds without even the basic plugins, that functionality is preserved |
| 25 |
for those who really want/need it. |
| 26 |
|
| 27 |
-- |
| 28 |
Duncan - List replies preferred. No HTML msgs. |
| 29 |
"Every nonfree program has a lord, a master -- |
| 30 |
and if you use the program, he is your master." Richard Stallman |
Archives