public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is it OK to get rid of app-alternatives/* ?
Date: Wed, 15 Feb 2023 19:20:37 +0000	[thread overview]
Message-ID: <d2b73a57-4ed2-111a-72a6-2255f6bf7222@youngman.org.uk> (raw)
In-Reply-To: <87757c79-0d78-9f7a-3f58-f95d71704ed6@gmail.com>



On 15/02/2023 15:51, Daniel Frey wrote:
> On 2/15/23 06:10, Michael Orlitzky wrote:
>> On 2023-02-15 08:11:46, Neil Bothwick wrote:
>>>
>>> If, as you say, it will eventually replace eselect, there is no more
>>> bloat, just different bloat. It's still just a bunch of symlinks, but
>>> managed differently.
>>>
>>
>> Should be less, since you already have portage installed but not
>> necessarily eselect-whatever.
>>
> 
> I didn't even know eselect-whatever was even an option until this 
> post... It's not something I've ever used.
> 
> It does (at least to me) make sense for the package manager to enforce 
> these selections rather than some optional tool though.
> 
what are they going to do about "eselect kernel set ..." then?

It's bad enough depclean deleting the active kernel if you don't watch 
out, without something deciding to install a non-existent kernel and 
deleting the live one :-)

Cheers,
Wol


  reply	other threads:[~2023-02-15 19:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  1:47 [gentoo-user] Is it OK to get rid of app-alternatives/* ? Walter Dnes
2023-02-15  1:54 ` David Rosenbaum
2023-02-15  1:57 ` Michael Cook
2023-02-15  7:44   ` Walter Dnes
2023-02-15  8:11     ` Neil Bothwick
2023-02-15 14:10       ` Michael Orlitzky
2023-02-15 14:41         ` Rich Freeman
2023-02-15 15:51         ` Daniel Frey
2023-02-15 19:20           ` Wol [this message]
2023-02-15 19:48             ` Arsen Arsenović
2023-02-16  4:09             ` Walter Dnes
2023-02-19 10:30               ` Neil Bothwick
2023-03-03  0:52                 ` David Rosenbaum
2023-02-15  8:53 ` Arsen Arsenović

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=d2b73a57-4ed2-111a-72a6-2255f6bf7222@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@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