[gentoo-dev] internal use only use flags

[gentoo-dev] internal use only use flags

[Marijn Schouten (hkBst)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGjoZrp/VmCx0OL2wRApD8AJ0WcZV5+Wws3KaLRPoSNmNZUfGwYQCgu0k8
SoTA2Nvp2y96lC59/9h7YT0=
=K3oW
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] internal use only use flags

[Petteri Räty]

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

Re: [gentoo-dev] internal use only use flags

[Mike Frysinger]

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

On Friday 06 July 2007, Marijn Schouten (hkBst) wrote:
> static - !!do not set this during bootstrap!! Causes binaries to be
> statically linked instead of dynamically

i dont really think this is in the same category at all with the other flags 
you mentioned here ... plus i'm not sure this is even a relevant warning 
anymore
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

Re: [gentoo-dev] internal use only use flags

[Chris Gianelloni]

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

On Fri, 2007-07-06 at 20:14 +0200, Marijn Schouten (hkBst) wrote:
> 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]

> It's probably a big pain to do this.

Changing build and bootstrap would require changes to a few packages in
system, but also to catalyst.  It would completely break all versions of
catalyst prior to the "fixed" version for stage building.

Basically, we'd have to support both for at least a little while until
we got all of the older versions of catalyst out of use/support.  I'd
need to stabilize catalyst 2.x and remove 1.x, at minimum.

It could be done, I just don't think the amount of work required for
what it otherwise a cosmetic change to be worth it.

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]