Package Details: grass 7.8.5-2

Git Clone URL: https://aur.archlinux.org/grass.git (read-only, click to copy)
Package Base: grass
Description: Geospatial data management and analysis, image processing, graphics/maps production, spatial modeling and visualization
Upstream URL: http://grass.osgeo.org/
Keywords: analysis GIS remote sensing spatial
Licenses: GPL
Submitter: Scimmia
Maintainer: kikislater
Last Packager: kikislater
Votes: 36
Popularity: 0.70
First Submitted: 2015-09-06 15:10
Last Updated: 2021-06-19 08:15

Dependencies (27)

Required by (3)

Sources (2)

Latest Comments

« First ‹ Previous ... 6 7 8 9 10 11 12 Next › Last »

Scimmia commented on 2015-10-04 16:49

Yep, congratulations, you badgered and pestered your way into getting the response you wanted all along.

czk commented on 2015-10-04 16:22

Now this is the kind of response I expected given your attitue so far. Get off your high horse, mister :D. Your build script has issues. Fix it or I'll fork it.

Scimmia commented on 2015-10-04 14:49

I'm done arguing about theoretical issues here. You abandoned the package, deal with it.

czk commented on 2015-10-04 11:59

And going back to $GRASS_PYTHON - even if indeed addons use it, you would need to make sure it's set to python2 by default in your GRASS package.

Really, a symlink is just as safe, simple and reliable as it gets. No error-prone shebang patching needed, no need to bother about $GRASS_PYTHON. It just works.

See more from GRASS devs on that issue: https://lists.osgeo.org/pipermail/grass-dev/2013-January/061356.html, https://lists.osgeo.org/pipermail/grass-dev/2013-January/061367.html.

czk commented on 2015-10-04 11:04

> For CPPFLAGS, look at the two lines above that. That's really what CPPFLAGS does anyway.

Why are you mixing CPPFLAGS into CXXFLAGS and CFLAGS and then drop CPPFLAGS? What if the build recognizes CPPFLAGS, like GRASS build does? See configure, lib/python/ctypes/Makefile, aclocal.m4. I believe you must have had a good reson to do it this way, but I don't understand it yet.

> --with-nls doesn't have any extra deps, but balloons the package pretty good.

Why are you concerned about few MBs?

> I'm thinking --with-liblas will be left out,

Why disable LIDAR support in GRASS 7?

Scimmia commented on 2015-10-04 00:05

For CPPFLAGS, look at the two lines above that. That's really what CPPFLAGS does anyway.

I'm not saying everything left out was of limited value; as I said, the point was to get this going with the defaults. It appears that --with-pthread and --with-netcdf are both useful without pulling in any extra deps, so I'll enable those. --with-nls doesn't have any extra deps, but balloons the package pretty good. Probably still worth it. I'm thinking --with-liblas will be left out, though.

I looked into how things were called when I was redoing things, I'm pretty sure things are specifically called with $GRASS_PYTHON. It is possible I misunderstood something, though.

czk commented on 2015-10-03 23:56

> I'm not dropping the user's CPPFLAGS.

I'm missing something then. What does the `unset CPPFLAGS' do?

> --with-cxx is the default

I missed --with-cxx being enabled by default in G7 these days.

> for things of limited value

Parallel r.mapcalc is not something to give up on too easily.

> aren't those addons called with "$GRASS_PYTHON" instead of just run directly?

Hmm, I don't know, yet. Are you sure that it works this way?

Scimmia commented on 2015-10-03 23:18

--with-cxx is the default, so I'm not touching that. I had thought about --with-pthread but hadn't looked into it.

As for the others, I'm reluctant to pull in too many deps, especially from the AUR, for things of limited value. I'll look into netcdf and nls more.

The main goal here was to get this all working again with default settings. We can look into things from there.

czk commented on 2015-10-03 22:59

Please bring back the following:

--with-nls enables interface translations,

--with-cxx enables building some cool modules written in C++: r.terraflow, i.attcor, r.viewshed,

--with-pthread enables parallel processing boost for r.mapcalc, the core GRASS raster module,

--with-netcdf: required for r3.out.netcdf, and maybe for old NetCDF format support in r.out.bin (not sure about the latter),

--with-liblas: I will ask you to bring it back when I upload liblas to new AUR. It is required for r.in.lidar and v.in.lidar.

Please mind that some great GRASS addons depend on the missing modules, too.

Scimmia commented on 2015-10-03 22:25

Read the PKGBUILD again, I'm not dropping the user's CPPFLAGS.

As for the advantage of using sed, it's an actual fix instead of a hack. Correct me if I'm wrong, but aren't those addons called with "$GRASS_PYTHON" instead of just run directly? If so, the shebang won't really matter.