[GRASS-user] Which ELGIS repository for SL6 on installing "wx" components

GRASS GRASS user
1

Hi and apologies for cross-posting.

In short,

which is the preferred ELGIS repository (for Scientific Linux 64) if I want to
get *only* dependencies to get into compilation of any grass-gis version?

I have a hard time to get wxGTK-devel installed. The installer complains about
"multilib" something stuff, referring to libXcursor (the 64-bit version is
installed, the i686 versions seems to be required?).

Do I really need to follow the instructions for CentOS as described in the
GRASS-Wiki (<http://grasswiki.osgeo.org/wiki/Compile_and_Install#CentOS&gt;\)?
I.e., install manually all of the "wx" components?

The longer story

I had a small experience in installing Scientific Linux and use the ELGIS
repository a few months ago. As I had not too much time, and in addition I
wanted to demo the process in people who wouldn't take time to compile stuff
from source, I dropped it in favour for (K)Ubuntu.

These days, I am setting up a new linux workstation (Xeon 2630 2.3MHz, 32GB
RAM). After a fresh SL6 installation and addition of the ELGIS (Testing), it
feels, in general, a bit slow. I didn't have yet the time to test real and
heavy raster/vector processing stuff though.

I have, also, some yum plugins enabled and this affects the overall cli
experience in terms of how quick the system manages packages (installation,
checking, updating, etc.).

I activated the ELGIS and ELGIS Testing repositories just to get all of the
(latest) OSGeo related dependencies installed. I have a hard time to get
wxGTK-devel installed. As I am writing from another machine, it's hard to
copy-paste details.

An extra question: can I seamlessly transfer my (K)Ubuntu bash
settings/profiles in SL6?

Thank you, N

2

On Fri, Jun 28, 2013 at 12:31 PM, Nikos Alexandris
<nik@nikosalexandris.net> wrote:

I have a hard time to get wxGTK-devel installed. The installer complains about
"multilib" something stuff, referring to libXcursor (the 64-bit version is
installed, the i686 versions seems to be required?).

The i686 versions are only required if you explicitly request them, or
if you have other i686 components installed which need them.

Do I really need to follow the instructions for CentOS as described in the
GRASS-Wiki (<http://grasswiki.osgeo.org/wiki/Compile_and_Install#CentOS&gt;\)?
I.e., install manually all of the "wx" components?

The CentOS instructions in the wiki seem a bit outdated.

You can get wxPython from the EPEL repository:

http://fedoraproject.org/wiki/EPEL

yum install wxPython

Other interesting repositories are elrepo for hardware and newer kernels

http://elrepo.org/tiki

and repoforge.org, but repoforge can conflict with EPEL (which I prefer).

BTW, I am not using ELGIS at all for my SL6 installations.

Markus M

The longer story

I had a small experience in installing Scientific Linux and use the ELGIS
repository a few months ago. As I had not too much time, and in addition I
wanted to demo the process in people who wouldn't take time to compile stuff
from source, I dropped it in favour for (K)Ubuntu.

These days, I am setting up a new linux workstation (Xeon 2630 2.3MHz, 32GB
RAM). After a fresh SL6 installation and addition of the ELGIS (Testing), it
feels, in general, a bit slow. I didn't have yet the time to test real and
heavy raster/vector processing stuff though.

I have, also, some yum plugins enabled and this affects the overall cli
experience in terms of how quick the system manages packages (installation,
checking, updating, etc.).

I activated the ELGIS and ELGIS Testing repositories just to get all of the
(latest) OSGeo related dependencies installed. I have a hard time to get
wxGTK-devel installed. As I am writing from another machine, it's hard to
copy-paste details.

An extra question: can I seamlessly transfer my (K)Ubuntu bash
settings/profiles in SL6?

Thank you, N
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

3

BTW, I am not using ELGIS at all for my SL6 installations.

Why not ?

4

On Fri, Jun 28, 2013 at 8:18 PM, Mathieu Baudier <mbaudier@argeo.org> wrote:

BTW, I am not using ELGIS at all for my SL6 installations.

Why not ?

Because the packages are too old for my requirements as a GRASS
developer. I am for example using proj-4.8.0, gdal-1.10.0, geos-3.3.8
with GRASS 7 and like the combination of a solid operating system with
recent packages where I want recent packages.

For production work, ELGIS seems fine with the exception of GRASS
which IMHO should be upgraded to the latest stable release 6.4.2.

Markus M

5

Why not ?

Because the packages are too old for my requirements as a GRASS
developer. I am for example using proj-4.8.0, gdal-1.10.0, geos-3.3.8
with GRASS 7 and like the combination of a solid operating system with
recent packages where I want recent packages.

For production work, ELGIS seems fine with the exception of GRASS
which IMHO should be upgraded to the latest stable release 6.4.2.

Actually ELGIS Testing (http://elgis.argeo.org/repos/testing/6/elgis/)
provide much more recent packages (GRASS 6.4.2 among them) and is as
stable (maybe even better quality...) than ELGIS Stable.

See package matrix here :
http://wiki.osgeo.org/wiki/Enterprise_Linux_GIS#Packages_matrix

There has been a big switch over the last few months since we now use
a fork of the Fedora/EPEL git repositories, in order to better
integrate with their efforts.

ELGIS Stable hasn't yet be replaced, simply because I have migrated
only the "core" packages (geos, GDAL, GRASS, PostGIS, MapServer, QGIS)
and not the secondary ones yet.

I must admit that I could not find enough time to keep the appropriate
level of quality and updates lately, since my company has become less
focused on GIS than it was two or three years ago (the main driver for
creating ELGIS back then).

Hopefully I will be able to finalize this switch properly over the summer.
I will then focus on getting other people involved in actually
packaging and building the packages, so that I'm not a bottleneck
anymore.

I'll let it know on various lists (GRASS among them, of course) when
we are back on track, because our mission statement is (was...)
precisely what you need: latest free GIS software on a stable basis.

Cheers,

Mathieu

PS: My company and myself are still committed to host the ELGIS builds
and repositories in the foreseeable future. We have resources
allocated for that, just too little with regard to my time.

6

Markus Metz:

>> BTW, I am not using ELGIS at all for my SL6 installations.

Mathieu Baudier:

> Why not ?

Markus Metz:

Because the packages are too old for my requirements as a GRASS
developer. I am for example using proj-4.8.0, gdal-1.10.0, geos-3.3.8
with GRASS 7 and like the combination of a solid operating system with
recent packages where I want recent packages.

+1

I am not a GRASS developer. Yet, I am a wannabe power-user. I always
compile
stuff under (K)Ubuntu wher I even compile proj, geos, etc. from source.
But I
want to avoid doing this all the time.

I am trying to set-up a stable SL6-based workstation and, of course, I have a
lot to learn.

This is why I enabled ELGIS Testing, where proj is for example 4.8 and
geos as
well newer than what in ELGIS stable. Note, for examlpe, there was a small
bug recently in GDAL (OGR) when converting ESRI Shapefiles to KMLs. How else
can a user benefit from latest fixes/updates if not compiling the whole piece
from the scratch.

For production work, ELGIS seems fine with the exception of GRASS
which IMHO should be upgraded to the latest stable release 6.4.2.

Well, I have no idea about the effort it takes to package stuff. I once
failed
to find the time to sit down and learn this for (K)Ubuntu -- seemed it would
take quite some time for a beginner.

How about pacakging for SL6? Does it take a lot of time/effort?

Thanks to all for your invaluable time,

Nikos

7

How about packaging for SL6? Does it take a lot of time/effort?

Upgrading micro version (say, GRASS 6.4.1 to 6.4.2) is just a matter
of changing the version and let some scripts run. Bigger upgrades,
merging from Fedora git repos, etc. require more skills and time (not
soo hard either).

I'm working on streamlining the simpler processes so that they can be
done by less experienced users.

I'll let it know on the ELGIS
(http://lists.osgeo.org/mailman/listinfo/el) mailing-list when it is
ready.

8

On Fri, Jun 28, 2013 at 9:02 PM, Mathieu Baudier <mbaudier@argeo.org> wrote:

Why not ?

Because the packages are too old for my requirements as a GRASS
developer. I am for example using proj-4.8.0, gdal-1.10.0, geos-3.3.8
with GRASS 7 and like the combination of a solid operating system with
recent packages where I want recent packages.

For production work, ELGIS seems fine with the exception of GRASS
which IMHO should be upgraded to the latest stable release 6.4.2.

Actually ELGIS Testing (http://elgis.argeo.org/repos/testing/6/elgis/)
provide much more recent packages (GRASS 6.4.2 among them) and is as
stable (maybe even better quality...) than ELGIS Stable.

See package matrix here :
http://wiki.osgeo.org/wiki/Enterprise_Linux_GIS#Packages_matrix

Nice! I did not look at the Testing repo before. The packages in ELGIS
Testing seem to me ready for production work.

There has been a big switch over the last few months since we now use
a fork of the Fedora/EPEL git repositories, in order to better
integrate with their efforts.

ELGIS Stable hasn't yet be replaced, simply because I have migrated
only the "core" packages (geos, GDAL, GRASS, PostGIS, MapServer, QGIS)
and not the secondary ones yet.

I must admit that I could not find enough time to keep the appropriate
level of quality and updates lately, since my company has become less
focused on GIS than it was two or three years ago (the main driver for
creating ELGIS back then).

Hopefully I will be able to finalize this switch properly over the summer.
I will then focus on getting other people involved in actually
packaging and building the packages, so that I'm not a bottleneck
anymore.

I'll let it know on various lists (GRASS among them, of course) when
we are back on track, because our mission statement is (was...)
precisely what you need: latest free GIS software on a stable basis.

Thanks a lot for your efforts!

Markus M

Cheers,

Mathieu

PS: My company and myself are still committed to host the ELGIS builds
and repositories in the foreseeable future. We have resources
allocated for that, just too little with regard to my time.