public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Boag-Munroe <ninpo@qap.la>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Update on the 23.0 profiles
Date: Mon, 8 Apr 2024 01:22:02 +0100	[thread overview]
Message-ID: <CANvbSho3fRUKf1cm9tAowX+kGHesJX3DzBKL1an0-GvztWmzXQ@mail.gmail.com> (raw)
In-Reply-To: <a8e55b4d9dc2db3c650eb93ace0ce32591fd08ed.camel@gentoo.org>

On Sun, 7 Apr 2024 at 22:09, Michael Orlitzky <mjo@gentoo.org> wrote:
<snip>
> What I am saying is that I want the freedom to not have things
> pointlessly enabled on my systems, because similar problems (and worse)
> happen all day every day. The less exposure I have, the better. The
> liblzma backdoor was timely because it will prevent most people from
> telling me I'm being paranoid, but it could have been USE=anything on
> any other day. Moving the defaults out of the high-level profiles will
> give control back to the user, hence my complaint about it.
>

I agree, to be honest. The spirit of profiles has always felt like it
switches on safe/sane defaults that you'd expect for the name (a
desktop plasma profile switches on all the useful desktop USE flags, a
basic profile enables the bare minimum for a bootable system, etc),
giving an expected functionality in the resulting outcome of a
re-merge of world.

Outside of this, preferred compression tools, preferred editors
etc...should be up to the user, or implied in the profile name if it's
going to be switched on in the profile defaults. I don't use zstd
myself, I prefer xz or lz4 depending on my purpose. It's on my system
because some things I chose to have required it. It feels un-Gentoo
for me to have zstd around _just because_, which the profile default
would bring into play.

--
Ninpo


  reply	other threads:[~2024-04-08  0:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06 15:06 [gentoo-dev] Update on the 23.0 profiles Andreas K. Huettel
2024-04-07  2:03 ` Michael Orlitzky
2024-04-07 12:35   ` Andreas K. Huettel
2024-04-07 12:51     ` Michael Orlitzky
2024-04-07 13:07       ` Andreas K. Huettel
2024-04-08  6:40         ` [gentoo-dev] " Duncan
2024-04-08 12:00         ` [gentoo-dev] " Michael Orlitzky
2024-04-08 15:16           ` Eddie Chapman
2024-04-07 14:48       ` Michał Górny
2024-04-07 21:09         ` Michael Orlitzky
2024-04-08  0:22           ` Alex Boag-Munroe [this message]
2024-04-08  3:07             ` Michał Górny
2024-04-07 11:35 ` Florian Schmaus
2024-04-07 12:31   ` [gentoo-dev] " Madhu
2024-04-07 13:27     ` Andreas K. Huettel
2024-04-11 16:37       ` [gentoo-dev] " Madhu
2024-04-07 12:32   ` [gentoo-dev] " Andreas K. Huettel

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=CANvbSho3fRUKf1cm9tAowX+kGHesJX3DzBKL1an0-GvztWmzXQ@mail.gmail.com \
    --to=ninpo@qap.la \
    --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