On Sun, 2021-01-24 at 16:11 +0100, Thomas Deutschmann wrote: > 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.
Could you back your claims with specific numbers? How many packages that do not strictly require eselect to operate are actually pulling it in? I don't see a single shell pulling in app-eselect/eselect-sh. sys-devel/binutils and sys-devel/gcc are probably the most common examples of packages not using eselect (except for one failed attempt). > 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. Is it really that bad to install the tools you actually use instead of forcing 'one size fits all' approach? -- Best regards, Michał Górny
