public inbox for gentoo-alt@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ruud Koolen <redlizard@gentoo.org>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Names of Prefix variants
Date: Mon, 18 Nov 2013 05:28:33 +0100	[thread overview]
Message-ID: <201311180528.33558.redlizard@gentoo.org> (raw)
In-Reply-To: <201310260054.48103.redlizard@gentoo.org>

Okay, this thread has been going nowhere for too long, and it's blocking 
progress. It's time to make a decision and be done with it.

I hereby christen the two variants of gentoo prefix "prefix guest" for the 
variant that has nongentoo include and library search paths and a nongentoo 
dynamic linker; and "prefix standalone" for which the dynamic linker and all 
search paths are strictly inside the prefix installation.

I will introduce a single new USE flag, masked in nonprefix profiles and 
forced in prefix guest profiles, "prefix-guest"; this USE flag with codify 
exactly the two properties specified above. I have decided not to use a 
second USE flag for the alternative after all; a look through the tree has 
shown that this would be useful at exactly one place (toolchain.eclass) and 
nowhere else, and at that point it's just a waste of complexity.

I will not use a USE_EXPAND variable, because there isn't really a (relevant) 
single setting that can take on multiple values across different prefix 
variants; rather, there is just the single deviation from normal gentoo 
system setups which may or may not apply to a given prefix variant, so a 
simple USE flag saying "this 'feature' is in effect" is the appropriate tool 
for the job.

I will create profiles default/linux/$arch/13.0/prefix/{guest,standalone}, of 
which the first is a link to prefix/linux/$arch and the second is the new 
profile to be written. I will not for now name either the "default" prefix 
profile on linux archs per the name default/linux/$arch/13.0/prefix, as I 
think that choice is best delayed until after we have more experience with 
how well the two variants work in practice; naming one the default is easy, 
but changing this decision later on is hard without breaking compatibility. 
Thus, for now default/linux/$arch/13.0/prefix will stay empty.

I will create a common base for the two variant profiles in features/prefix, 
with both variant profiles inheriting it. After all, the majority of profile 
hacks in the current prefix profiles would apply in full force in 
prefix-standalone.

Unless there are any complaints, I'm planning to make all this a reality in a 
few days.

Thoughts?

-- Ruud


  parent reply	other threads:[~2013-11-18  4:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 22:54 [gentoo-alt] Names of Prefix variants Ruud Koolen
2013-10-26  0:23 ` Greg Turner
2013-10-26  0:28   ` Ruud Koolen
2013-10-26  7:41 ` Fabian Groffen
2013-10-26  8:13   ` Ruud Koolen
2013-10-26  9:28     ` Fabian Groffen
2013-10-31 15:50       ` heroxbd
2013-10-29  7:40 ` Michael Haubenwallner
2013-10-29 22:02   ` Ruud Koolen
2013-10-31  5:03     ` Jeremy Olexa
2013-10-31  7:37     ` Michael Haubenwallner
2013-11-18  4:28 ` Ruud Koolen [this message]
2013-11-18  9:24   ` Fabian Groffen
2013-11-18 15:33     ` Ruud Koolen
2013-11-19 10:20       ` heroxbd
2013-11-19 11:37         ` Michael Haubenwallner
2013-11-19 15:48         ` Fabian Groffen
2013-11-19 10:13   ` heroxbd

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=201311180528.33558.redlizard@gentoo.org \
    --to=redlizard@gentoo.org \
    --cc=gentoo-alt@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