William, you've converted me to Frameworks, they are clearly the
cleanest way to avoid the many conflicts inherent using lots of
libraries and versions. Your work is a prize, and I thank you very
much. GRASS is now running fine.
Just as an aside, our local science/tech community were just talking
about the difficulties of version control, and one of us came out with
such a wonderful rant I thought I'd share it! It goes like this:
On Jun 12, 2008, at 11:45 AM, Roger Critchlow wrote:
The maze of package management, revision management, version
control, and
configuration control tools, and whether they exist or not, is the
real pain
of moving between programming environments. I can almost keep the
language
syntax and libraries straight, but when it comes to figuring out how
to run
CPAN for perl again, or how the 'easy_install' package works for
python, or
what the alternative for Tcl is that ActiveState.com has
implemented, or the
ruby gems repository, or why "yum update" and "apt-get update" do
completely
different things, I give up.
It's a Turing complete mess.
Owen Densmore <[EMAIL PROTECTED]> wrote:
Yup, indeed my interest related to the netlogo gis extension: it
currently does not handle DEM raster data, only ASC, which apparently
is a fairly standard format .. also called ESRI Grid I think.
I guess its time for me to start using basic GIS libraries with
either
Python or Java. My main problem with Python is their library system
and lack of backward compatibility. The libraries are always in cat-
fights with each other and they all fail to run on the same version
of
Python itself, thus requiring a rather awkward balancing.
_______________________________________________
grass-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-user
