The putback for 6915312 ON should be able to build IPS packages natively is a FLAG DAY for all ON developers.
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. For ALL Developers ----------------- ALL ON developers must use the new tools to build these bits. Either get your bldenv/nightly from the /ws location once they're updated, or build in usr/src/tools/scripts, and invoke bldenv and/or nightly from your built copy. If you're building interactively, you may need to include $TOOLS_PROTO/opt/onbld/bin in your path. The -p option to nightly has been updated to build an IPS repository in $CODEMGR_WS/packages/$MACH/nightly[-nd]/repo.(extra|redist) Set ON_CRYPTO_BINS in your nightly environment file. We strongly recommend that people doing builds with closed sources (almost all internal developers) set the following in their env files: ON_CRYPTO_BINS= \ /net/onnv.sfbay/export/onnv-gate/packages/$MACH/on-crypto.$MACH.tar.bz2 export ON_CRYPTO_BINS This will enable you to use the gatekeeper-signed crypto and not require the internal-only crypto packages which are only available in the on-extra repository. If you need to run the crypto that you just built (e.g., you're making crypto changes or have major user/kernel boundary changes), unset this variable before building. Before image-updating your test system, make sure that you set your on-extra publisher. ALL ON developers need up-to-date build machines. You must either be building on OpenSolaris 133 or greater (recommended), or install SUNWipkg on your legacy SXCE/Nevada system. For your legacy SVR4 systems, you can either build the IPS gate yourself to generate SVR4 packages of IPS, or grab them from this internal location: http://nana.sfbay/products/osol_dev/133/svr4_ips_packages_i386.zip http://nana.sfbay/products/osol_dev/133/svr4_ips_packages_sparc.zip Support for building on SXCE/Nevada is expected to be removed soon, so upgrade to OpenSolaris as soon as possible. If you build on SXCE, the automatic dependency generation feature will be turned off. You can install the resulting packages, but you must take extra care to make sure your dependencies are all installed, because pkg won't be able to do it for you. Remove content from usr/src/pkgdefs. We have removed all of usr/src/pkgdefs. After you pull these changes into your workspace, if you have made changes there, you will need to make the corresponding changes in usr/src/pkg. Then, regardless of whether you have made any such changes, you must manually remove usr/src/pkgdefs from your workspace. As a sanity check, both "ls -l usr/src/pkgdefs" and "hg manifest | fgrep pkgdefs" should show nothing. Even an empty usr/src/pkgdefs directory will confuse nightly, because it still understands how to build in workspaces with any combination of pkgdefs and pkg. Incrementals might work, but no guarantees. An incremental will probably work, but we won't guarantee it in all scenarios, so a clobber build and a clean proto are likely wise. Non-incremental nightly should do the trick. Test on OpenSolaris. Per jbeck's message from August 5th 2009, you should be testing your changes on OpenSolaris. http://static.opensolaris.org/on/flagdays/pages/2009080502.html This change sediments that requirement, and you must focus your testing on pkg image-update. Your test systems should first be updated to OpenSolaris 133 or greater before following any of these procedures. A new tool "onu" is available to ease setup for OpenSolaris systems. The manpage is available in the source tree and soon in an onbld location near you. BFU is still available (though ACR is not), but pkg image-update is the preferred testing method. Support for BFU is expected to be removed in a few builds. Debug gatekeeper nightly builds should be published starting tomorrow hopefully around 9:30 AM PT (sorry, internal-only) http://ipkg.sfbay/on-nightly http://ipkg.sfbay/on-extra and the repository contents will be archived in the usual /ws/onnv-gate/packages location. Package RTIs are changing. The process for package RTIs is changing. Check with the CTeam about latest requirements. Read README.pkg and the FAQ first. Please read the README in usr/src/pkg/README.pkg. It contains specific information about how IPS and ON are integrated. We'll also be updating the FAQ at http://hub.opensolaris.org/bin/view/Community+Group+on/ON+IPS+FAQ Finally, bugs against the tools can be filed in bugster category solaris/consolidation/os-net-tools Thanks, The ON IPS Team
