[GRASS-dev] Re: [GRASS-SVN] r44977 - in grass/trunk: gui/wxpython/xml imagery imagery/i.evapo.PT

[Maris Nartiss]

Good point, stll other software projects manage it somehow.
* Stricter rules for API changes
* API version checks
* API Changelog with HowTo migrate hints.

Nothing impossible, just a bit of rules and enforcing. R manages
somehow to have gazzillion of addons with easy install - can we borrow
ideas there?

Still - is it worth to NOT have lots of modules in core? Confusion
could be reduced by toolbox-like naming, better GUI menus and search
etc.

Just keeping mind open for other options,
Maris.

2011/1/13 Glynn Clements <glynn at gclements.plus.com>:
>
> Michael Barton wrote:
>
>> Having user-installable toolboxes is a nice idea in theory. But
>> there are at least 2 important pragmatic issues to be addressed
>
> 3) In 7.0, anything not in the main repository will be prone to
> bit-rot as the API changes. If a developer changes an API, they can
> reasonably be expected to fix any modules which used that API, but
> this doesn't hold for add-ons.
>
> --
> Glynn Clements <glynn at gclements.plus.com>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>