On Thu, Apr 22, 2010 at 03:38:14PM -0700, Bart Smaalders wrote: > On 04/22/10 15:31, Will Fiveash wrote: > >Assuming I've run nightly with -p first, I want to make sure I > >understand the effect of: > > > >1. modify bits that are in BRCMbnx and do a dmake install in that dir > >2. cd to $SRC/pkg > >3. dmake -e PKGS="BRCMbnx" all > >4. dmake -e PKGS="BRCMbnx" install > >5. run "/usr/lib/pkg.depotd -d repo.redist -p 13000" in nightly package. > >6. run pkg image-update on my test system with the on-nightly publisher > > pointing to the pkg.depotd I started. > > > >What packages will be in the new BE created by the image-update? Will > >all the packages found in the BE where pkg image-update was run be in > >the new BE? Assuming BRCMbnx was in the previous BE will the BRCMbnx > >package be the only package modified in the new BE? > > That will be the case IF the other packages in opensolaris.org or any > other configured repos haven't changed since image-update grabs 'em all.
O.K., I just wanted to make sure that by setting PKGS when building and installing in the $SRC/pkg dir I wasn't going to break pkg image-update that is setup to use that pkg repo. > Assuming you're running the same build version as you've built, you > could just create a new be, mount it on /mnt and use > pkg -R /mnt install BRCMbnx to pickup the new version in your new BE. Ah, right I keep forgetting about that. Thanks for that tip. -- Will Fiveash Oracle Austin, TX, USA Internal Solaris Kerberos/GSS/SASL website: http://kerberos.sfbay.sun.com http://opensolaris.org/os/project/kerberos/ Note my new work e-mail address: [email protected] _______________________________________________ on-ips-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
