Grobian wrote: > Please find attached GLEP 47: "Creating 'safe' environment variables". > > The GLEP is a Gentoo/Alt initiative. Constructive comments are welcome. >
> > The variables ``ELIBC``, ``KERNEL`` and ``ARCH`` are currently set in > the profiles when other than their defaults for a GNU/Linux system. > They can as such easily be overridden and defined by the user. To > prevent this from happening, the variables should be auto filled by > Portage itself, based on the ``CHOST`` variable. > > A map file can be used to have the various ``CHOST`` values being > translated to the correct values for the four variables. This change is > invisible for ebuilds and eclasses, but allows to rely on these > variables as they are based on a 'safe' value -- the ``CHOST`` variable. Assuming the CHOST variable is 'safe' is not a good thing, users can over-ride this variable. Can you specify some behavior when it's set to something bogus ( invalid form ) or something thats not in the mapping? > Ebuilds should not be sensitive to the keyword value, but use the > aforementioned four variables instead. They allow specific tests for > properties. If this is undesirable, the full ``CHOST`` variable can be > used to match a complete operating system.
signature.asc
Description: OpenPGP digital signature
