> The current available and supported option is to use the Distro-Constructor > and > create your own stripped down enterprise build.
I must admit I've not used the DC yet, however reading thru: http://www.opensolaris.org/os/project/caiman/Constructor/ http://opensolaris.org/os/project/caiman/Constructor/DC_docs/DC_toi.html I can not immediately see how this would potentially help in the context discussed here. all it does is to process pre-configured packages, already configured following the rules as in: http://wikis.sun.com/display/IpsBestPractices/Packaging+Best+Practices+-+Dependencies taking the inital example: http://www.opensolaris.org/jive/thread.jspa?threadID=104903&tstart=0 the removal fails likely because of an existing "require" dependency which other packages do have on the to-re-removed one. (btw, how can I see those dependencies in detail ? the update manager just shows the dependencies but not more details, pkg(1) does not appear to have an option to show dependencies at all ?) this implies vice-versa, that a package that has a "require" dependency on lets say, SUNWevolution-data-server will automatically install that package (Evolution) even if I do not want it to be installed, usual package install or DC shouldn't matter here. I'd expect in both cases the same end result, eg. Evolution will be installed. The only way I could imagine DC would help here is if I'd edit the packages upfront and hack around in the package dependencies to get rid of the "require" attribute prior using the DC to produce my homebrew install distro. of course this may be different in practice, but this is what I take out of it right now. ---- frankB -- This message posted from opensolaris.org