| 1 |
On Sun, Aug 3, 2008 at 4:36 AM, Zac Medico <zmedico@g.o> wrote: |
| 2 |
> Arfrever Frehtes Taifersar Arahesis wrote: |
| 3 |
>> 2008-08-02 04:02:48 Zac Medico napisa³(a): |
| 4 |
>> The names of other RESTRICT values are related to features which are |
| 5 |
>> restricted. The new proposed value is intended for live ebuilds so its |
| 6 |
>> name should be negation of this feature. I think that something like |
| 7 |
>> RESTRICT=constant-sources would be better. |
| 8 |
> |
| 9 |
> Like I've said before, that particular convention is pretty |
| 10 |
> worthless in my eyes. I'd much prefer RESTRICT=live-sources if we |
| 11 |
> want to use a longer name. |
| 12 |
|
| 13 |
How about we just skip the reversed-boolean-usage/it's-a-long-name |
| 14 |
confusion/argument and just call it RESTRICT=tarballs ? |
| 15 |
|
| 16 |
I know not all distfiles are tarballs, but it gets the message across |
| 17 |
far better than "constant-sources" IMO :o) |
| 18 |
|
| 19 |
-- |
| 20 |
~Nirbheek Chauhan |
Archives