| 1 |
On 04/24/2013 12:48 PM, René Neumann wrote: |
| 2 |
> Am 24.04.2013 19:15, schrieb Zac Medico: |
| 3 |
>> On 04/24/2013 02:51 AM, René Neumann wrote: |
| 4 |
>>> As more and more packages seem to (mis)use USE_EXPAND: Can we get the |
| 5 |
>>> possibility to set this directly in package.use? Having to write |
| 6 |
>>> 'claws_mail_plugins_foo' does not help readability, and setting it in |
| 7 |
>>> make.conf is also not the right way (as is package.env). |
| 8 |
>> |
| 9 |
>> How about if we use a share a single PLUGINS USE_EXPAND among multiple |
| 10 |
>> unrelated packages? That way, you're package.use settings will be less |
| 11 |
>> verbose (plugins_foo versus claws_mail_plugins_foo). |
| 12 |
>> |
| 13 |
>>> And could anyone explain to me, why having 21 additional use-flags is |
| 14 |
>>> bad? I mean, you have them now too, the only 'advantage' being a nicer |
| 15 |
>>> display on 'emerge -v'. |
| 16 |
>> |
| 17 |
>> Using a generic PLUGINS USE_EXPAND will also have the advantage of |
| 18 |
>> making the emerge -v display less verbose. |
| 19 |
>> |
| 20 |
> |
| 21 |
> Yes, this sounds like a good compromise. I'd still go with Michał if I |
| 22 |
> had to choose ... but I'm not the maintainer :). |
| 23 |
|
| 24 |
We've got a feature request bug here for a package.use USE_EXPAND syntax |
| 25 |
extension: |
| 26 |
|
| 27 |
https://bugs.gentoo.org/show_bug.cgi?id=471776 |
| 28 |
-- |
| 29 |
Thanks, |
| 30 |
Zac |
Archives