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