public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] internal use only use flags
  @ 2007-07-06 18:16 99% ` Petteri Räty
  0 siblings, 0 replies; 1+ results
From: Petteri Räty @ 2007-07-06 18:16 UTC (permalink / raw
  To: gentoo-dev

[-- 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 --]

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2007-07-06 18:14     [gentoo-dev] internal use only use flags Marijn Schouten (hkBst)
2007-07-06 18:16 99% ` Petteri Räty

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox