On Wed, Mar 19, 2008 at 11:55:51AM -0700, Bernard Li wrote: > > > they can't be committed "as-is" either because the assumptions made are > > configurable and users will expect that they match (regardless of how many > > notes about not being supported are added) but will be useful if ever make > > is > > expanded to make a target to build [open]solaris packages. > > What's involved with making a package for Solaris?
it is a very simple process with a couple of files (basically the file list) that are processed by the SysV package management that Solaris uses. it is important to note though, that packaging in Solaris is not mean to be process of transforming sources into binaries, but in managing binaries and their dependencies. OpenSolaris, seems a better fit, model wise to what is being done currently with ganglia sources to generate binaries (rpm and dpkg), since the two most popular distributions seem to be taken a more fitting focus with their packaging system : Indiana (IPS) Nexenta (APT/DPKG) > It would be good > to have these things in a generic way (much like the RPM spec file and > init scripts) such that they can be checked into the repo and > potentially picked up by Blastwave or something. no idea about blastwave, but sunfreeware has ganglia packages : http://www.sunfreeware.com/programlistintel10.html#ganglia Carlo ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
