On 09/04/2017 23:52, Michael Orlitzky wrote:
On 04/09/2017 12:15 PM, William L. Thomson Jr. wrote:
Not sure if this is practical, it may be less work if the use of
Python and Ruby versions ( maybe others ) is reversed. Rather than
adding all the versions that the ebuild supports. What if it only
included versions it did not support?
Even if this would work better, it would require retraining all
developers, completely rewriting several eclasses, tons of
documentation, and a few thousand ebuilds.
Let's assume the retraining will be 2 or 3 orders of magnitude easier
than switching from cvs to git, than that's doable.
Eclasses, ebuilds and documentation will be the real burden, but at this
point it's better to discuss if the feature is wanted or not, then later
wait for the volunteer(s) to actually do the work.
No one's going to jump on that bandwagon without a proof-of-concept
that works much better than what we have now.
yep, that could be done, but since it's not trivial maybe better decide
if it will be wasted or possibly accepted.
by the way eclasses from gentoo repo with PYTHON string inside are the
following:
$ grep -c PYTHON *.eclass | grep -v :0$
distutils-r1.eclass:28
enlightenment.eclass:6
gnome-python-common-r1.eclass:2
kernel-2.eclass:2
mate.eclass:1
mozcoreconf-v4.eclass:3
python-any-r1.eclass:75
python-r1.eclass:107
python-single-r1.eclass:112
python-utils-r1.eclass:203
ros-catkin.eclass:40
twisted-r1.eclass:2
waf-utils.eclass:7
