[GRASS5] A comment and a question.

Eric G. Miller egm2 at jps.net
Thu Oct 25 00:07:54 EDT 2001


On Wed, 24 Oct 2001 20:53:30 -0600, "Roger S. Miller" <rgrmill at rt66.com> wrote:

> 
> Folks,
> 
> It took a few days, but Hal Mueller convinced me that it probably is a
> good idea for a "production" installation of GRASS 5.0 for the installed
> files to be owned by root.  That wasn't necessarily true for the beta
> and pre-release versions, and we're certainly not talking about the
> GRASSS database.  For a stable system the installation scripts should
> probably have an option to make root the owner of the installed files,
> as are (for instance) the program files in a Postgres installation. 
> Last week Hal provided the list with some specific suggestions about how
> that might be done.

If someone wants to look at using "install" rather than tar, it will
do the right thing (and probably be faster than tar anyway).  The
"install" program can also strip symbols, which could be useful
since initial binaries could have debugging symbols, and "install"
would remove them.  Then a recompile wouldn't be necessary to grab
a debuggable version of a module.

> As to the question...  I seem to recall that my first GRASS 5
> installation included an s.surf.krige program, but it isn't there in
> either of my current installations.  Is my memory completely messed up,
> or was it removed?  I searched the archives and found a couple letters
> that mentioned kriging, but no explanation for what happened to the old
> program.  What happened to the old one, and are there any plans to
> replace it?

It was/is s.surf.krig.  Bugs ... from old copy of grass CVS:

[RC]s.surf.krig                                                                    
  Not working. Needs various bugfixes.                                     
  Calls to G_distance() seem to suffer stack corruption. The values        
  of parameters passed in and out of G_distance() are corrupted.      
  (being worked on by David D Gray)



-- 
Eric G. Miller <egm2 at jps.net>



More information about the grass-dev mailing list