On 7/13/10, James Lee <[email protected]> wrote: > > CSWcswclassutils has to be manually installed in the global zone, > splitting it will make package management harder. > > Having a single responsible person should be a good thing, like having > a prime contractor. The best way to reduce the maintainer burden is > to stop fiddling with it.
There's a tradeoff involved. Yes, there's "more stuff to install in global zone". However, once it is done initially... there is potentialy much less change. Some of the more recent additions, were very volatile in change rate. A cautious site, could have avoided any global changes whatsoever, if they did not happen to use one of the packages that used the class action script being tweaked. It also allows more choices at the site-local level. This way, it would be easier for a site to override ONE particular class action script (for example, with their own package that had date set for REV=3000.0.0), yet otherwise get normal updates for the other ones. At the moment, they would have to keep reviewing all 22 scripts, on every update to classutils. _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
