Below a suggestion for the packaging structure:
regarding addon packaging. We can create packages like
grassaddons(full addons)
grassaddons-imgagery
grassaddons-vector
grassaddons-raster
grasssaddons-general
I question when looking at :
http://trac.osgeo.org/grass/browser/grass-addons
I
Tim wrote:
I question when looking at :
http://trac.osgeo.org/grass/browser/grass-addons
I wonder:
* why is there a separate branch per major grass version?
between grass 5, 6, and 7 the library APIs change and the
module options/flags change, so a module written for one
often won't work on
Dear community of GRASS users,
is there a need for having packages for the GRASS addons?
Please give feedback by:
(+1 / 0 / -1)
And of saying yes (+1), would you voluteer in heping with packaing and
maintaining the daily builds of the PPA?
Please give feedback by:
(+1 / 0 / -1)
Below a
Tim Michelsen timmichel...@gmx-topmail.de writes:
+1
unfortunately not able to help.
Dear community of GRASS users,
is there a need for having packages for the GRASS addons?
Please give feedback by:
(+1 / 0 / -1)
And of saying yes (+1), would you voluteer in heping with packaing and
Tim wrote:
Below a suggestion for the packaging structure:
regarding addon packaging. We can create packages like
grassaddons(full addons)
grassaddons-imgagery
grassaddons-vector
grassaddons-raster
grasssaddons-general
if you do it, please name the pacakges like grass-addons-*,
and install
