public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] internal use only use flags
Date: Fri, 06 Jul 2007 21:16:08 +0300	[thread overview]
Message-ID: <468E86E8.1020609@gentoo.org> (raw)
In-Reply-To: <468E866B.8080905@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

Marijn Schouten (hkBst) kirjoitti:
> A grep '!!' /usr/portage/profiles/use.desc reveals the following:
> 
> bootstrap - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used during
> original system bootstrapping [make stage2]
> build - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used for
> creating build images and the first half of bootstrapping [make stage1]
> livecd - !!internal use only!! DO NOT SET THIS FLAG YOURSELF!, used during
> livecd building.
> selinux - !!internal use only!! Security Enhanced Linux support, this must be
> set by the selinux profile or breakage will occur
> static - !!do not set this during bootstrap!! Causes binaries to be statically
> linked instead of dynamically
> 
> I think these internal use only use flags should have names that indicate
> that, for example: INTERNALUSE_bootstrap. This would help in recognizing them
> and at the same time free those names for normal use. The newest GHC is now
> forced to use "ghcbootstrap" and I plan on adding similar support to SBCL for
> the next release.
> 
> It's probably a big pain to do this.
> 

USE_EXPAND anyone... They can even be hidden from emerge -pv output I think.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-07-06 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 18:14 [gentoo-dev] internal use only use flags Marijn Schouten (hkBst)
2007-07-06 18:16 ` Petteri Räty [this message]
2007-07-06 18:41 ` Mike Frysinger
2007-07-09 19:16 ` Chris Gianelloni

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=468E86E8.1020609@gentoo.org \
    --to=betelgeuse@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