| 1 |
On 11/21/2014 11:04 AM, Pacho Ramos wrote: |
| 2 |
> El vie, 21-11-2014 a las 11:03 +0100, Pacho Ramos escribió: |
| 3 |
>> El jue, 20-11-2014 a las 23:04 +0100, Michał Górny escribió: |
| 4 |
>> [...] |
| 5 |
>>> Here's how games-r1 would look like. However, now that I think about it, |
| 6 |
>>> it may be actually useful to commit such an eclass. Otherwise people |
| 7 |
>>> will keep thinking games.eclass is the way to go. |
| 8 |
>>> |
| 9 |
>> |
| 10 |
>> Why isn't games.eclass deprecated then (like was done with old python |
| 11 |
>> eclasses) to let people to progressively stop using that at all? |
| 12 |
>> |
| 13 |
>> |
| 14 |
> |
| 15 |
> I clicked to "send" too fast sorry :S |
| 16 |
> |
| 17 |
> I meant that maybe we should simply deprecate it in the way that repoman |
| 18 |
> will inform people that they need to stop using it ;) |
| 19 |
> |
| 20 |
> |
| 21 |
|
| 22 |
There are users who seem to like it and the games team wants to keep it |
| 23 |
as well, so I don't see a reason to push into that direction. |
| 24 |
|
| 25 |
The main thing is that you cannot turn off all the permission stuff in |
| 26 |
the eclass whether you like it or not. Changing the install variables |
| 27 |
thing is just for convenience and already possible. |
Archives