| 1 |
On Sun, 2021-01-24 at 16:11 +0100, Thomas Deutschmann wrote: |
| 2 |
> eselect is a known interface for most (all?) slotted packages. |
| 3 |
> Configuration management tools expect that the appropriate module will |
| 4 |
> be pulled in once you install a slotable package. |
| 5 |
|
| 6 |
Could you back your claims with specific numbers? How many packages |
| 7 |
that do not strictly require eselect to operate are actually pulling |
| 8 |
it in? |
| 9 |
|
| 10 |
I don't see a single shell pulling in app-eselect/eselect-sh. |
| 11 |
|
| 12 |
sys-devel/binutils and sys-devel/gcc are probably the most common |
| 13 |
examples of packages not using eselect (except for one failed attempt). |
| 14 |
|
| 15 |
> You are now forcing everyone to either migrate to a new system (manage |
| 16 |
> python-exec.conf directly) or ensure they update their world file and |
| 17 |
> manually ensure that eselect-python is still installed which will make |
| 18 |
> Python special. |
| 19 |
|
| 20 |
Is it really that bad to install the tools you actually use instead of |
| 21 |
forcing 'one size fits all' approach? |
| 22 |
|
| 23 |
-- |
| 24 |
Best regards, |
| 25 |
Michał Górny |
Archives