public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] sys-meta/* to own and control /bin/{cpio,sh,tar,...} symlinks (alternatives-ish)
Date: Wed, 23 Nov 2022 11:32:55 -0500	[thread overview]
Message-ID: <Y35LN2WbkTZDUMYw@eversor> (raw)
In-Reply-To: <46faec78-e9c9-1cd6-6c69-c8192f2861df@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2022-11-23 16:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  7:38 [gentoo-dev] [RFC] sys-meta/* to own and control /bin/{cpio,sh,tar,...} symlinks (alternatives-ish) Michał Górny
2022-11-23 13:47 ` Michael Orlitzky
2022-11-23 14:37   ` Michał Górny
2022-11-23 14:58     ` Michael Orlitzky
2022-11-23 16:45       ` Ulrich Mueller
2022-11-24  1:32         ` Alexey Sokolov
2022-11-24  2:05           ` Ionen Wolkens
2022-11-24  2:10             ` Ionen Wolkens
2022-11-24  4:01             ` Maciej Barć
2022-11-23 15:49     ` Ionen Wolkens
2022-11-23 17:36       ` Ionen Wolkens
2022-11-24  0:14       ` Yuan Liao (Leo)
2022-11-23 13:58 ` Piotr Karbowski
2022-11-23 14:26   ` Michał Górny
2022-11-23 16:32   ` Ionen Wolkens [this message]
2022-11-23 17:48 ` Michael Orlitzky
2022-11-24 16:29 ` Michał Górny
2022-11-24 17:25   ` Maciej Barć
2022-11-24 19:01     ` Alec Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y35LN2WbkTZDUMYw@eversor \
    --to=ionen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox