Re: [GRASS-user] Ubuntu Packages for Addons [was: Re: Fwd: Re: ppa for grass 7 Ubuntu Quantal]
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 another without some slight modification. > * what is the policy for backwards / upwards compatibility? within major version backwards compatibility. A module written for 6.0.0 will still work with any future 6.y.z versions. It is likely for compiled modules the ABI is not stable, and you will have to recompile for the current version. Any python and shell scripts should be forward-compatible though. If you try to run a compiled addon module against a different libgis than the one it was built for, you will get the "please untangle versions" error. "g.version -r" shows the libgis rev for this reason: g.version -r: Print the GIS library revision number and time GRASS 6.4.1 (2011) Revision: 43636 Date: 2010-09-22 22:18:42 +0200 (Wed, 22 Sep 2010) GRASS 6.4.2 (2012) Revision: 45934 Date: 2011-04-13 13:19:03 +0200 (Wed, 13 Apr 2011) GRASS 6.4.3svn (2013) Revision: 50937 Date: 2012-02-26 02:14:51 +1300 (Sun, 26 Feb 2012) GRASS 6.5.svn (2013) Revision: 50936 Date: 2012-02-26 02:14:47 +1300 (Sun, 26 Feb 2012) it doesn't change very much, but often enough to mean that you need to recompile your addons when switching between minor versions. (e.g. it's been more than a year since it changed last) > * shall we instead of grouping by command type group by > version? an addon package containing grass7 addons should exclusively depend on the grass7-core package etc. so at minimum it must be grouped by major version. Hamish: > > and install to /usr/lib/grass64/addons/. We'd have to > > patch our lib/init/init.sh in the main ubuntu package > > to add that dir to the GRASS_ADDON_PATH if it existed > > on the system. Tim: > Why do we not make this default, then? because Debian installs grass in a funny place (/usr/lib/grassXY), any system packages need to be available to all users equally- so in a common OS dir, and personal addons can't go into a system dir where the user does not have write access. It's not a big deal to do the patch. regards, Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Ubuntu Packages for Addons [was: Re: Fwd: Re: ppa for grass 7 Ubuntu Quantal]
>> 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 wonder: * why is there a separate branch per major grass version? * what is the policy for backwards / upwards compatibility? * shall we instead of grouping by command type group by version? > if you do it, please name the pacakges like "grass-addons-*", > and install to /usr/lib/grass64/addons/. We'd have to patch our > lib/init/init.sh in the main ubuntu package to add that dir > to the GRASS_ADDON_PATH if it existed on the system. Why do we not make this default, then? > I'd base the decision on if to package them all together or > in groups based on how big the resulting package was. if it's > just a couple of MB, keep it simple in one pkg-- note for > official debian packaging all the docs and help page images > would need to be split out into another platform-inspecific > -data &/or -docs package(s). So your 4-5 packages above grow > to 12-15 of them.. for a weekly ppa build it doesn't matter > though. (the reason for that on Debian is to avoid duplicated > space in the archives since 11 different hardware platforms, > each needing their own binary pkg but can share the -data one) Let's get the thing going on experimental basis and then see how we could organise it. ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Ubuntu Packages for Addons [was: Re: Fwd: Re: ppa for grass 7 Ubuntu Quantal]
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 to /usr/lib/grass64/addons/. We'd have to patch our lib/init/init.sh in the main ubuntu package to add that dir to the GRASS_ADDON_PATH if it existed on the system. I'd base the decision on if to package them all together or in groups based on how big the resulting package was. if it's just a couple of MB, keep it simple in one pkg-- note for official debian packaging all the docs and help page images would need to be split out into another platform-inspecific -data &/or -docs package(s). So your 4-5 packages above grow to 12-15 of them.. for a weekly ppa build it doesn't matter though. (the reason for that on Debian is to avoid duplicated space in the archives since 11 different hardware platforms, each needing their own binary pkg but can share the -data one) note some of the things in addons are either experiments or still in development, AFAIK by placing the module in the ../Makefile the developer is announcing that it is fit for human consumption. thanks, Hamish ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Ubuntu Packages for Addons [was: Re: Fwd: Re: ppa for grass 7 Ubuntu Quantal]
Tim Michelsen 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 > maintaining the daily builds of the PPA? > > Please give feedback by: > (+1 / 0 / -1) > > >> 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 can give it a try if everyone agrees on package naming and is necessary > > I started off on with creating the general infrastructure: > https://code.launchpad.net/grass-addons > > * just wait for the import to finish > * start off with the debian files as usual. > * then run the recipe: > https://code.launchpad.net/~grass/+recipe/grass-addons-daily > > Regards, > Timmie > > > ___ > grass-user mailing list > grass-user@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user <#secure method=pgpmime mode=sign> -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] Ubuntu Packages for Addons [was: Re: Fwd: Re: ppa for grass 7 Ubuntu Quantal]
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 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 can give it a try if everyone agrees on package naming and is necessary I started off on with creating the general infrastructure: https://code.launchpad.net/grass-addons * just wait for the import to finish * start off with the debian files as usual. * then run the recipe: https://code.launchpad.net/~grass/+recipe/grass-addons-daily Regards, Timmie ___ grass-user mailing list grass-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-user
