Bart Smaalders writes: > Darren J Moffat wrote: > > Bart Smaalders wrote: > >> Packages should represent a minimization boundary; e.g. they > >> are either installed or not installed depending on the > >> proposed use of the system. > >> > >> Solaris has areas where packages are too fine-grained, > >> it also has areas where the packages are much too large > >> to be useful in this fashion. > > > > and also has multiple packages for somethings where the "minimization > > boundary" would dictate only one due to how diskless clients and sparse > > root zones do sharing of /usr and how the installers provide for that. > > > > That's a broken artifact of the current implementation :-(. > Note that zones directory sharing breaks packaging in new > and wonderful ways.
It'd be nice if packaging clusters were full-fledged citizens of Solaris, and not just implemented out in the margins. Clusters represent those tied-together bits of functionality, and not the internal architecture exposed by packages. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
