| 1 |
Am 06.06.2010 15:44, schrieb Arfrever Frehtes Taifersar Arahesis: |
| 2 |
> 2010-06-06 12:40:28 Thomas Sachau napisał(a): |
| 3 |
>> Additionally, it should define the supported slots, something like this: |
| 4 |
>> |
| 5 |
>> SUPPORTED_RUBY_SLOTS="1.8 1.9" or |
| 6 |
>> SUPPORTED_PYTHON_SLOTS="2.5 2.6 3.0 3.1" |
| 7 |
>> |
| 8 |
>> Now the package manager should take those vars and convert them to some expanded USE vars like: |
| 9 |
>> |
| 10 |
>> RUBY_SLOTS="1.8 1.9" or |
| 11 |
>> PYTHON_SLOTS="2.5 2.6 3.0 3.1" |
| 12 |
> |
| 13 |
> We are already working on automatic generation of USE flags in python.eclass (in newer EAPIs). |
| 14 |
> |
| 15 |
|
| 16 |
And why do you want to implement such code in every eclass? |
| 17 |
|
| 18 |
Whats wrong with implementing it on the package manager side once and reusing it for every |
| 19 |
eclass/ebuild, which needs such code? |
| 20 |
|
| 21 |
-- |
| 22 |
Thomas Sachau |
| 23 |
|
| 24 |
Gentoo Linux Developer |
Archives