2012/3/20 c. <carlo.defa...@gmail.com>: > > On 20 Mar 2012, at 21:39, Jordi Gutiérrez Hermoso wrote: > >> I want a unified build method that builds Octave and then builds and >> tests all OF packages against the same Octave build that just >> happened. > > That was done when we had the "monolithic" forge releases. > Having to build all octave-forge packages or none was about to kill > octave-forge. > The project was only revived when Søren developed the new system for managing > packages independently.
There's no reason why all of OF has to build. Recursive make(1) calls can fail and be logged. It would be nice to have *some* method of at least trying to build and test all of Octave Forge regularly. This is independent of the release schedule of each package, but it shouldn't be independent of the current Octave development version. Problems should be caught as soon as possible, when they're fresh in everyone's mind. I would much rather know when a commit of mine to Octave broke 30 OF packages than to have to dig later throug VCS logs to figure out what broke and when. - Jordi G. H. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
