On Thu, Jan 07, 2010 at 02:36:38PM +0000, Daniel Pocock wrote: > > then you are going to need either 2 public resources for all release > > managers > > to use consistently or a coordinate release process were the package is > > generated and then independently binary packages are added to it before > > the announcement (which also means we have to agree on what is going to be > > used for building those RPM packages). > > > > > Not necessarily - it may be sufficient to provide some scripts that > release managers can use, as long as the hostnames can be easily > configured somewhere. Then the release manager just needs to have the > necessary machines available, but that is not so difficult either thanks > to Xen, VMware, etc.
With mock[1] you probably don't need anything beyond one machine, mock basically runs rpmbuild inside a minimal chroot (which also installs for you) of a Fedora/Centos (might also be usable for Suse) release that you want and the rpm dependencies of the package. Given that most developers will have a Fedora/Centos/RHEL/Debian machine building rpms shouldn't be a problem really. Cheers, Kostas [1] http://fedoraproject.org/wiki/Projects/Mock ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
