public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Madhu <enometh@meer.net>
To: gentoo-dev@lists.gentoo.org, Florian Schmaus <flow@gentoo.org>
Subject: [gentoo-dev] Re: Update on the 23.0 profiles
Date: Sun, 07 Apr 2024 18:01:52 +0530 (IST)	[thread overview]
Message-ID: <20240407.180152.1533542310117167076.enometh@meer.net> (raw)
In-Reply-To: <c7386cc8-34c3-4b9b-8033-59252a19df75@gentoo.org> (Florian Schmaus's message of "Sun, 7 Apr 2024 13:35:45 +0200")

> Thanks for the update and the work on the 23.0 profiles. :)
>> Most 17.x profiles have been downgraded to "exp".
> I could imagine there is a reason to downgrade those back to 'exp',
> could you elaborate a bit on that?
>
> Isn't it bit strange that a 'stable' profiles gets downgraded back to
> 'exp'? Then again, I am not sure about the implications of this nor
> about the rationale behind it.
>
> However, I also notice that there is a outstanding PR that reverts
> that [1]. Maybe we should introduce a new state 'oldstable' or so?

I see no way of migrating to 23.0 profile because of not-recompilable
packages that are installed (over 4 years) which block --emptytree,
and do not wish to be forced to migrate to merged-usr on an openrc box
without a compelling need (on principle).

Will patching back the 17.0 profile files into the portage tree if and
when they are removed work?

Are there any options at all for this situation (like freezing the the
last supported tree protecting it from emerge-syncs, and using an
overlay for further updates?)





  reply	other threads:[~2024-04-07 12:31 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
2024-04-08  3:07             ` Michał Górny
2024-04-07 11:35 ` Florian Schmaus
2024-04-07 12:31   ` Madhu [this message]
2024-04-07 13:27     ` [gentoo-dev] " 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=20240407.180152.1533542310117167076.enometh@meer.net \
    --to=enometh@meer.net \
    --cc=flow@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