[2nd resend due to mailing list problem]

>>>>> "Rainer" == Rainer Orth <[EMAIL PROTECTED]> writes:

Rainer> * DMAKE_MAX_JOBS in nightly env file isn't honored,

Known bug:

    6343373 nightly.sh ignores existing DMAKE_MAX_JOBS

Rainer> * I think it would be useful if bldenv set it's -d option from
Rainer>   the -D flag in a nightly env file.

Yeah, I've been burned several times by forgetting the -d.  What you
propose makes sense if -DF is set.  If only -D is set, -d is probably
the right behavior, but I'm not sure.

Rainer> * The files and directories in the SUNWonbld packages
Rainer>   distributed on opensolaris.org belong to a non-system uid
Rainer>   (stevenl/staff if viewed with GNU tar), which is ugly if you
Rainer>   extract them somewhere as root.  I think they should use
Rainer>   cpiotranslate as well to only use system uids and gids.

Yeah, I don't see any reason for SUNWonbld not to follow the same
conventions as other packages.

Rainer> * SUNWonbld should comply with Sun's own packaging guidelines
Rainer>   and install into /opt/SUNWonbld instead of /opt/onbld.  This
Rainer>   change requires a couple of other places to be updated as
Rainer>   well, but I've a list of affected files and would obviously
Rainer>   update them at the same time.

This seems reasonable to me.  A temporary compatibility link redirecting
/opt/onbld to /opt/SUNWonbld seems like a good thing, particularly since
it forces the old /opt/onbld to go away.

Rainer> * There's some confusion and duplication between the environment
Rainer>   variables used by nightly to e.g. augment PATH to find onbld
Rainer>   (/opt/onbld) and the build tools (/opt/SUNWspro) and a
Rainer>   different set of variables used in make files.  

This is at least partially covered by

    6241194 ON has too many spro configuration variables

I'll add your comments and a call record.

Rainer> How should we procede from here?  If there's agreement that
Rainer> those are all bugs, I can file bugs via bugs.opensolaris.org and
Rainer> provide fixes for most of the issues.

Excellent!

mike
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to