Why not do it the other way around: make eselect-python leading, and
have it populate PYTHON_TARGETS?
It could be a lot more work, but might be more intuitive.
On 1/24/21 4:11 PM, Thomas Deutschmann wrote:
Hi,
I am hot happy with this change.
Why must dev-lang/python become special?
eselect is a known interface for most (all?) slotted packages.
Configuration management tools expect that the appropriate module will
be pulled in once you install a slotable package.
You are now forcing everyone to either migrate to a new system (manage
python-exec.conf directly) or ensure they update their world file and
manually ensure that eselect-python is still installed which will make
Python special.
But because dev-lang/python does not call eselect-python anymore it
looks like you cannot retain old, well established behavior across all
slotable packages anymore.
