On 11/09/13 15:03, Peter FELECAN wrote: > Dagobert Michelsen <[email protected]> writes: > >> Hi folks, >> >> we get bug reports from time to time about people who don't initially get >> the concept of global-zone packages, e.g. >> https://www.opencsw.org/mantis/view.php?id=5121 >> >> What do you think about a package CSWglobalzone which is a metapackage >> depending on all packages needed in the globalzone? (CSWcas-*) > > This meta package should depend on all the packages delivering files > outside /opt/csw. Unfortunately there are many of them which can be > polemically discussed about the pertinence of their inclusion: > > CSWalternatives > CSWcas-cpsampleconf > CSWcas-cptemplates > CSWcas-crontab > CSWcas-etcservices > CSWcas-etcshells > CSWcas-inetd > CSWcas-initsmf > CSWcas-migrateconf > CSWcas-postmsg > CSWcas-preserveconf > CSWcas-pycompile > CSWcas-sslcert > CSWcas-texhash > CSWcas-texinfo > CSWcas-usergroup > CSWdosexec > CSWsamba-nss-system-links > CSWsamba-pam-system-links > CSWtap > CSWtun
This is very good idea. From time to time it's hard to upgrade (accidentaly made) sparse root zones. Having one single metapackage containing all packages needed is a good idea. > -- Juraj Lutter <[email protected]>
