On 27/03/2012 10:05, Carlo Marcelo Arenas Belon wrote: > On Mon, Mar 26, 2012 at 04:57:31PM +0100, Daniel Pocock wrote: >> >> Having the option to work both ways may just continue to create traps >> for people who know one half of the project and not so much about the other. > > ironically, the main driver for the 3.3.x series was to import the new web > frontend, and it used to (mostly) work for the first 2 releases of that > series while keeping the posibility of building independently.
Those releases worked for some people and not others Another idea: the web tree can have Makefile.am, managed by monitor-core/configure.in and that can be the official release and packaging mechanism But for those who want to make standalone builds, the web/Makefile can be renamed as web/Makefile.standalone and executed manually make -f Makefile.standalone > it would seem IMHO that all the extra hacking that was done to the build > and release process, including the (mostly ignored) documentation hadn't > improved on its reliability or clarity as shown by the fact that the last > package release just masquerades the obsolete version 3.3.1 as 3.3.5 for > web. It has resulted in a review of past processes, more wiki documentation, and I think we have now reached the point where I can build the Solaris packages again, these are all good outcomes that the project can build on ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
