Hi Glynn, I would like to have that kind of Makefile, so I can build all grass add-ons related to GRASS 7 SVN without changing anything in the structure of the SVN
Could anyone help us to get somewhere near to that effect, even if we would need a configure option like --build-addons-dir=../grass-addons/grass7 that would be neat. Thank you, Yann On 1 November 2012 03:03, Glynn Clements <[email protected]> wrote: > > Moritz Lennert wrote: > > > > I suggest that modules should not simply be moved from addons to > > > trunk, but that a developer has a close look at a module including > > > testing before moving it to trunk. > > > > +1, but I see Martin's point about lack of dev power. So the trade-off > > has to be between quality of code and value added of having a > > functionality in trunk even if the code is not perfect. > > Relegating something to add-ons is a reliable way to reduce the amount > of developer oversight it gets. E.g. currently you can't just "make" > the add-ons/grass7 directory (it lacks a Makefile), so most developers > won't even try to compile it. If the modules were in trunk, developers > may notice errors or warnings as part of the normal build process. > > -- > Glynn Clements <[email protected]> > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- Yann Chemin
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
