On Thu, Mar 23, 2006 at 01:00:59PM +0000, Gavin Maltby wrote:
>
> ...
> Building should be very strict, as nightly is, and strip down your
> workspace of all that may be bad. In fact I'd like to see it start
> with an 'env -i' or equivalent. Too many times I've had to help
> people debug their build only to find the gnu assembler present in
> their build path! But on the editing side you do want to permit more
> config, eg to find favoured editors etc. I'd guess that we could
> readily separate the build/edit requirements of a user in some rc
> file.
This is
6217023 nightly should provide a clean build environment
which unfortunately got lumped in with another project which is firmly on
my back burner. I'll try to get some cycles to untangle it in the next week
or so; it's a fairly simple change (which may generate some pain in the
developer community...).
I've updated the bug to include my current evaluation in the
Description; it'll show up on bugs.opensolaris.org after the next push.
The meat of the change is the following list of "allowed" envvars:
CODEMGR_WS, PATH, HOME useful for custom env scripts
TERM, TERMCAP, TERMINFO useful for shell users
DISPLAY, XAUTHORITY useful for X11 users
OPTHOME, TEAMWARE used by nightly
SHELL used by bldenv
NIGHTLY_ENV_* explicit pass-throughs
Both nightly(1) and bldenv(1) will do the exact same environment
cleansing. Initially, they will both have a '-E' flag to disable
environment clearing, to allow for a (short!) transition period. A
couple of builds later, the -E flag would be removed.
Note that the ENV file can define and export whatever additional variables
it wants, so there's no loss of functionality here.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
