On Wed, Nov 23, 2022 at 02:58:14PM +0100, Piotr Karbowski wrote:
> I am very much in favour to have a package that controls those symlinks. 
> What is not immediately clear to me is what would that mean for eselect 
> in long run. Is it so that you'd like to keep eselect around and alive 
> parallel to those sys-meta category packages, or would there be push to 
> eventually get rid of most of eselect and where possible switch to sys-meta?

There's some that do nothing but modify config files (e.g. eselect
editor, even has freestyle which couldn't express as USE), and there's
other over-the-top stuff like Wine or gcc (between wine variants, and
crossdev gcc, feel managing sys-meta and switching on the fly would
get annoying).

So yeah, think both type have a place.

On Wine note, new eselect-wine-2 won't modify /usr anymore and it's
easy to track/cleanup/reset what it modifies now -- something eselect
can try to aim for in general.

-- 
ionen

Attachment: signature.asc
Description: PGP signature

Reply via email to