>> >> >If I (at the risk of sounding like a broken record) >> go back to clusters >> >and metaclusters, then imagine clusteradd operating >> on clusters as first >> >class objects - so it installs the whole lot in a >> single operation >> >(rather >> >like a single pkgadd of all the combined packages), >> and only updates the >> >contents file once. >> >> I'd much prefer it if we could optimize the operation >> so that: >> >> pkgadd p1 >> pkgadd p2 >> pkgadd p3 >> >> is speeded up as much as >> >> pkgadd p1 p2 p3 >> >> as that gives the same gain without having to retool >> everything around it. > >"pkgadd p1 p2 p3" operation for Solaris has been implemented by TWW's HPMS for >Solaris.
That's not what I was talking about: the pkgadd operation for multiple packages is already defined; I just want to point out that any performance work needs to optimize for the serial pkgadd case and not just the parallel (multiple packages added at once) case because I wouldn't want the optimization to depend on retooling all the tools that now perform serial package add (patch tools, upgrade, install) >Even auto installation for chain of package dependency that exist in other OS >(like HP-UX's SD-UX ) is avaiable for Solaris already. But does it use "pkgadd" and the Solaris native package database? Casper
