Kyle J. McDonald wrote at 11/28/06 14:09: >>Thanks for sharing the info, Kyle. It is indeed a bit unusual >>way to install and expand the system. If you could blog the detail and >>share the link, I think that will be an interesting info for whom >>want to do the same or similar. >> > > I can post the package add/deletes from my JS profile after I reproduce it.
That'll be wonderful information. There was some related activities called "minimization" but I'm not quite sure whether there was any conclusion on that. I cc'd opensolaris-discuss mailing list for possible comment from other folks on that. > > >>Usually what people do is select a meta-cluster a bit bigger than >>the Core such as End User and higher and customize/remove unneeded >>packages with and during Solaris installation where dependency >>information would be provided in more detail. >> > > Yes but removing things from the larger clusters is a pain. The dependcies > usually scare you out of removing things since tracking down all the other > packages to remove is such pain. > > Have you ever tried remoinvg the WBEM packages from SUNWCdev? Ouch. > > I was hoping to get the smallest install I could, with the least baggage from > other packages. So I started as small as possible, and added from there. > > As it is I found several dependencies trails that make no sense... Like why > does GNOME accessibility depend on Solaris Zones? > > Or try installing XscreenSaver without GNOME - or with as little GNOME as > possible, pretty soon you're installing Python, TCL, TK, Accesibilty, parts > of Evolution, Encryption, GNOME printing, Solaris Printing packages, etc. > > It's much easier to manage the dependencies while adding packages than > removing them. I think either way probably has pros and cons. As I usually install entire distribution with all locales installed, I cannot say how difficult it is to customize your installation although I have done my shares of customizations in the past. Due to I have some idea on Solaris clustering and dependencies, it was quite and rather convenient to use Solaris installation program to customize but I may (and probably) not representing majority of the users. > > >>SUNWuiu8 which contains iconv code conversion modules and binary >>tables belong to SUNWCutf8 cluster and the cluster belongs to SUNWCuser >>(i.e., End User) and higher meta-clusters and statically installed when >>such meta-clusters are chosen during the Solaris installation. I'd be >>also personally interested in knowing what are the packages have in your >>system before you added SUNWuiu8 and get the en_US.UTF-8 going by the way. >> > > You're right, I was mistaken when I said SUNWCutf8 wasn't referenced by any > of the meta clusters. And I can see why SUNWCreq and SUNWCrnet don't include > it. > > How ever when I was adding the GNOME packages, I would have expected the > installer to prompt me to resolve the SUNWuiu8 depenency even if I started > with SUNWCrnet. > > Just to clarify, Adding SUNWuiu8 didn't make en_US.UTF-8 work. I still don't > have en_US installed. Adding SUNWuiu8 made the 'C' Locale work without en_US. > > I'll try to generate the list of packages tommorrow. I'd be still interested to know what GNOME package(s) are using or having the dependency to the SUNWuiu8 for C locale since this could be a packaging bug on lacking dependency definition at GNOME package(s) albeit minor (as SUNWCutf8 being belong to all meta- clusters that are capable of supporting GUI desktop environment). I'm also cc'ng desktop-discuss mailing list. > > > This message posted from opensolaris.org > _______________________________________________ > i18n-discuss mailing list > i18n-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/i18n-discuss For the past messages from Kyle, BTW, please see the following threads: http://www.opensolaris.org/jive/thread.jspa?threadID=18807&tstart=0 http://www.opensolaris.org/jive/thread.jspa?threadID=18722&tstart=0 Ienup
