Howdy-- This note is directed primarily at folks building onnv-gate. As of tonight's nightly bits, I believe that others can get away with using either version of nightly.sh, and shouldn't really care about +/-t builds.
In spite of its length, our first flag day left out some useful info: The TOOLS_PROTO-related changes to nightly.sh constitute a flag day in both directions: newly updated workspace won't build with the old script, and vice versa. This problem is compounded by some difficulties distributing the new tools, so between /ws/onnv-tools, and different OpenSolaris and SXCE public build servers, it's hard to tell what's in your path. So: if you know what tools are in your path, decide appropriately what to use. If you're not sure, then use nightly.sh from the workspace that you're building; that should always match up. Though we suggested that an incremental was OK, there's a lot of change in the proto area. Doing a full clobber build will really make you happier. If you do -U builds, you will need to set PARENT_TOOLS_ROOT in your env; see usr/src/tools/env/gatekeeper.sh for an example. In fact, if you have not done so in a while, you should check out the current default env files in usr/src/tools/env. The -0 (that's zero, not cap-oh) option to nightly.sh is gone. Once you're using the new nightly.sh, you'll need to remove it from your nightly options. And, finally, from the original flag day note [1]: > For FAQs and pointers to more information, please refer to > > http://hub.opensolaris.org/bin/view/Community+Group+on/ON+IPS+FAQ > > We realize this is a big change, so please send questions to > > on-ips-dev at opensolaris.org where a number of us are available > > to help. --Mark [1] http://mail.opensolaris.org/pipermail/on-discuss/2010-March/001603.html
