Matt Ingenthron wrote:
Shawn Walker wrote:
Shawn's answer covers the needed functionality, but the issue is that
there are some classes of things you don't want to have to go create
a new BE for. For instance? I was working on building some
software, noticed the new SunStudioExpress, went to install it, and
inadvertantly, through the GUI, went down the image-update path.
A new user may assume that's the only path, and rebooting to use a
newer compiler is pretty silly.
Which will only happen if you use 'Update All' or 'image-update'.
If you just select the package itself and use install, then only that
one package will be updated, and no alternate boot environment will be
created.
You seem to be missing my point. I got that, and I understand ipkg
underneath, but the UI tends to lead one toward "update all"... which
will probably make new OpenSolaris users think that's the only route.
Right, and as I said, unfortunately we don't have the necessary
information available yet to make that decision smarter.
I'm not missing the point; I'm just explaining the limitations and how
you might be able to workaround them.
Cheers,
--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
