| 1 |
2010-06-06 15:54:23 Thomas Sachau napisał(a): |
| 2 |
> Am 06.06.2010 15:44, schrieb Arfrever Frehtes Taifersar Arahesis: |
| 3 |
> > 2010-06-06 12:40:28 Thomas Sachau napisał(a): |
| 4 |
> >> Additionally, it should define the supported slots, something like this: |
| 5 |
> >> |
| 6 |
> >> SUPPORTED_RUBY_SLOTS="1.8 1.9" or |
| 7 |
> >> SUPPORTED_PYTHON_SLOTS="2.5 2.6 3.0 3.1" |
| 8 |
> >> |
| 9 |
> >> Now the package manager should take those vars and convert them to some expanded USE vars like: |
| 10 |
> >> |
| 11 |
> >> RUBY_SLOTS="1.8 1.9" or |
| 12 |
> >> PYTHON_SLOTS="2.5 2.6 3.0 3.1" |
| 13 |
> > |
| 14 |
> > We are already working on automatic generation of USE flags in python.eclass (in newer EAPIs). |
| 15 |
> > |
| 16 |
> |
| 17 |
> And why do you want to implement such code in every eclass? |
| 18 |
> |
| 19 |
> Whats wrong with implementing it on the package manager side once and reusing it for every |
| 20 |
> eclass/ebuild, which needs such code? |
| 21 |
|
| 22 |
We can accept such an implementation if it meets all our requirements. |
| 23 |
E.g. Python ebuilds must specify list of NOT supported Python ABIs (e.g. using whitespace-separated |
| 24 |
list of fnmatch patterns). When a new slot of Python is available, then updating one place |
| 25 |
(an eclass or a file in profiles) must be sufficient to add a USE flag to all ebuilds (which |
| 26 |
don't specify a range of not supported Python ABIs which would match the new Python ABI). |
| 27 |
|
| 28 |
-- |
| 29 |
Arfrever Frehtes Taifersar Arahesis |
Archives