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