On 08/17/10 02:55 PM, Glenn Lagasse wrote:
* Keith Mitchell ([email protected]) wrote:
  libti/Makefile and man/Makefile copyright dates look like they're
not quite right. Other changes look good.
Fixed.

In the flag day, don't forget that we'll need to "beadm unmount
on-nightly" before rebooting. Would it be possible to have a special
slim_source repo ready as well as the on-nightly one, so that
internally we can update once rather than twice? (This should also
mean that we don't have to "pkg fix install/beadm").
I'll add some text about making sure to unmount before rebooting.  We
can probably have a slim_source repo available as well, though I'm not
sure what that buys us.  I don't see how having it will get us around
the pkg fix install/beadm issue.

I missed the fine print that mentioned the second half of the instructions were for testing slim_source changes, not for the build system itself. There's not necessarily a need, given that.

I do think (hope?) it might remove the need for the pkg fix - I believe IPS will "do the right thing" if libbe.so.1 is removed from 1 pkg at the same time it's added to another (when run in a single operation). If not, there will be an issue upgrading to 147 off of ipkg.sfbay requiring *everyone* to run pkg fix install/beadm.

Regardless, there's no need for you to set-up a special repo with it. Our build machines will have one, naturally (duh!)

- Keith

   I also don't know how we'll reconcile
these BE's once the 147 WOS build is available.  To clarify, with my
proposed instructions you will end up with a BE that is based on a WOS
build (currently 145) + ONNV_147.  My hope is that once the WOS build of
147 is available, getting back onto that train will only require pkg
refresh --full and then an image_update.  After which you can then just
remove the on-nightly publisher.  Creating a BE that is WOS_145 +
ONNV_147 + slim_source_147 seems potentially confusing to pkg (and me)
and I'm not sure that migrating back to a pure WOS based build will work
(and I can't test any of these scenarios because we don't have a WOS_147
build for me to test against).  Given all that, I'd prefer to keep the
steps as explicit as can be.

Glenn

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

Reply via email to