On Wed, Oct 08, 2008 at 01:03:14AM +0100, John Levon wrote: > Am I just missing up to date instructions on building IPS somewhere, or > do they genuinely not exist? (util/distro-import/README is not current > at least.)
As a starting point, this is all I needed in the end... # HG changeset patch # User John Levon <[EMAIL PROTECTED]> # Date 1224025912 25200 # Node ID 65aa16ec0f2cde154ec02d32618989eddcc7dd4d # Parent bf5fccb053a230e19c92b473b5f141b6d6af216f add a readme diff -r bf5fccb053a2 -r 65aa16ec0f2c README --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README Tue Oct 14 16:11:52 2008 -0700 @@ -0,0 +1,59 @@ +Building IPS +------------ + +An incomplete set of notes on how to build IPS. This presumes that +you're using a Solaris Nevada build machine already set up for building +the ON consolidation. + +Make very sure that your OpenSSL packages are recent enough to live in +/usr not /usr/sfw (that is, post 6449514, integrated into snv_96). + +Presuming the above, building IPS itself is very simple: + +cd src +make install packages + +This will generate SVR4 IPS packages in the top-level packages/ +directory. + +Importing a Solaris build into an IPS repository +------------------------------------------------ + +First, you need to install the IPS packages on to your build machine +that you built above, or alternatively pick them up from the proto area +as follows: + +WS=/path/to/your/build/tree +PROOT=$WS/proto/root_`uname -p` +export PYTHONPATH=$PROOT/usr/lib/python2.4/vendor-packages/ +export PATH=$PROOT/usr/bin/:$PROOT/usr/lib:$PATH + +Now you can start your IPS server, either via SMF or quickly by hand: + +export PORT=10666 +export REPO=http://localhost:$PORT +nohup pkg.depotd -p $PORT -d /var/tmp/$USER/repo & + +Note that any local user can write to these repos, so be careful! + +Now point two variables to the location of your Nevada media: + +export WOS_PKGS="/mnt/Solaris_11/Product/" + +and the extra Indiana packages (on SWAN): + +NONWOS_PKGS="/net/paradise.sfbay/export/integrate_dock/nv/nv_osol0811/all" +NONWOS_PKGS="$NONWOS_PKGS /net/paradise.sfbay/export/integrate_dock/nv/nv_osol0811/`uname -p`" +export NONWOS_PKGS + +And you can now do a full import: + +export BUILD=99 +cd $WS/src/util/distro-import +make -e $BUILD/redist_import + +After this finishes, you will be able to "pkg image-update" to the +contents of this repo. If you need to rebuild only some packages, you +can also do: + +export JUST_THESE_PKGS="SUNWcs" diff -r bf5fccb053a2 -r 65aa16ec0f2c src/util/distro-import/README --- a/src/util/distro-import/README Tue Oct 14 12:53:17 2008 -0700 +++ b/src/util/distro-import/README Tue Oct 14 16:11:52 2008 -0700 @@ -1,27 +1,3 @@ -Importing a Solaris build into IPS. ------------------------------------ - -% BUILD_IMAGE=/net/netinstall/export/nv/x/72/Solaris_11/Product -% ./clustertoc2import $BUILD_IMAGE/.clustertoc > cluster.import -% cat > my_import -include all.i386 -include cluster.import -^D -% ./solaris.py -w $BUILD_IMAGE my_import - -The output from solaris.py is large; if new packages appear that -aren't mapped in all.i386, errors about ignoring svr4 packages will -appear. These need to be resolved before publishing will be successful. - -Some more work is needed to make this easier to use and move from -build to build. - -To add only some packages, specify their name after the above command -as in: - -% ./solaris.py -w $BUILD_IMAGE my_import SUNWcsd ... - - 10/16/2007 ---------- @@ -39,7 +15,7 @@ 07/09/2008 ---------- -Some explanantion of solaris.py's arguments would appear useful: +Some explanation of solaris.py's arguments would appear useful: solaris.py [-dn] -b defaultbranch [-B perpkgbranches] [-D elided-file] [-w additional_pkg_search_path] [-I includefile] [-j pkg_to_process] _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
