[GRASS-user] Missing some tools: v.db.addcol, for example
Nikos Alexandris
nikos.alexandris at felis.uni-freiburg.de
Fri Oct 16 09:08:12 EDT 2009
On Fri, 2009-10-16 at 15:01 +0200, Nikos Alexandris wrote:
>
> > > On Thu, Oct 15, 2009 at 5:00 PM, Roger André <randre at gmail.com> wrote:
> > > > My PATH while in GRASS already contains the scripts dir:
> >
> > > > GRASS 6.4.0RC4 (colombia):~ > echo $PATH
> > > > /usr/local/grass-6.4.0RC4/bin:/usr/local/grass-6.4.0RC4/scripts:<snip>
> >
> > Mine too (the grass-6.4.0svn version).
> >
> >
> > > > What I did find is that each script is under a directory by the same
> > > > name in the scripts dir. So for example, d.redraw is in:
> > > > /usr/local/grass-6.4.0RC4/scripts/d.redraw/d.redraw
> >
> > On Fri, 2009-10-16 at 11:44 +0200, Markus Neteler wrote:
> > > Wow. This is not desired of course. I am a bit surprised.
>
> On Fri, 2009-10-16 at 12:18 +0200, Nikos Alexandris wrote:
>
> [Replying to myself]
>
> > Maybe I don't get that right but I have grass64_release, grass640_0rc5,
> > grass6_devel, grass_trunk. In all of them the scripts (sub-)directory
> > contains a directory for each script. In each script-directory there are
> > description (html) files and also README, Makefiles, etc.
> >
> > Isn't this ok?
>
> Yes it is (for the source code :-). Under /usr/local/grass... (the
> installed stuff; currently I use the 64 version) all scripts are bare
> files under the scripts directory.
>
>
> > > > I'm going through all of these now, and removing the dir and leaving
> > > > the script. Somewhat tedious, but the scripts appear to work.
> >
> > > Would you mind to check if this is still valid for RC5?
I've installed grass-6.4.0RC5 and there is no problem. Scripts (all of
them I suppose seem to) work fine ~ I 've tested several.
Nikos
More information about the grass-user
mailing list