From: Sam James <sam@gentoo.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Profile 23.0 testing with stages and binhost (part 2 of 2)
Date: Fri, 15 Mar 2024 23:23:10 +0000 [thread overview]
Message-ID: <874jd7yt9d.fsf@gentoo.org> (raw)
In-Reply-To: <23517098.6Emhk5qWAg@noumea> (Andreas K. Huettel's message of "Fri, 15 Mar 2024 19:12:54 +0100")
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
"Andreas K. Huettel" <dilfridge@gentoo.org> writes:
> Hi all,
>
> the 23.0 profiles are ready for testing, including stage downloads,
> binary packages, and update instructions for existing installations,
> for all arches.
>
> [...]
>
> Note 2: While there are 23.0 split-usr profiles, the *stage* downloads
> are *all* of the merged-usr type. Why? Not because I'm a big fan of that,
> but because we should try to unify and standardize a bit again - to
> avoid too many different build configurations leading to too many Heisenbugs.
I don't think this is a good idea.
We've promised people that they can keep unmerged-usr if they want, but
not having stages means new installs aren't doable, and it also makes
testing a pain because you can't easily unmerge.
You can easily merge, but you can't easily unmerge.
What you can do is provide a limited number of non-merged-usr variants
given it's just about saving people rebuilds.
(I also think it's the wrong way to do such a change anyway - the releng
part should be last after decision-making, not first.)
> [...]
> Cheers & have fun,
thanks,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next prev parent reply other threads:[~2024-03-15 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 18:12 [gentoo-dev] Profile 23.0 testing with stages and binhost (part 2 of 2) Andreas K. Huettel
2024-03-15 23:23 ` Sam James [this message]
2024-03-16 9:34 ` Andreas K. Huettel
2024-03-16 12:12 ` [gentoo-dev] " Duncan
2024-03-16 16:16 ` 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=874jd7yt9d.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=dilfridge@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