Julian Wiesener wrote: > Hello Stephen, > > On Mon, 2008-07-28 at 15:16 -0700, Stephen Hahn wrote: > >> I didn't know that beadm required GNOME. When does GNOME get called >> in beadm? >> > > i too don't think that beadm will call any gnome components, but beadm > is part of the package SUNWgui-install wich contains files with gnome > dependencies. Since image-update will always reinstall the gnome > components if they are requered, it is not an option just to remove the > packages. A seperated Package with beadm and a core-cluster without any > gui-related packages would be the optimal solution for me. > > Thanks for Feedback, i'll try to remember, that > http://bugs.opensolaris.org/ is not the only place to search for > existent Bug-Reports. > > _______________________________________________ > indiana-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/indiana-discuss > Complete opposite would also be nice, though it's risky when you start using post release versions of GNOME or any complex compliation of software on an older build of kernel/libc/etc components as OpenSolaris is not directed at the moment to establish trust for being fully upgradable without breakage between flag days and large code drops, such as leaping from GNOME 2.20 to 2.22.1. Nonetheless I'd like to be able to update just those SUNWjds* packages on Indiana, should work fine for the most part and I'm willing to solve interdependency issues related to not upgrading "core" packages if ips is not up to figuring out what's best. Still could be better than trying to do it on Nevada (SXCE without ips), where you can't rollback transactions.
James _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
