Sorry, just noticed there was a call to action by me in that bug report
which I missed. Anyway, I think the key issue here is whether or not the
database connection file is considered an essential part of a valid GRASS
location.
1. If it *is*, then creation of it should be added to the places th
On Thu, 13 Mar 2008, GRASS GIS wrote:
for 6.3.0 I have re-enabled automatic VAR creation if it doesn't exist.
more soon.
Attached is a patch (completely untested) that illustrates my idea for
solving the problem. I think there should also be something in
lib/gis/make_mapset.c (used by
Eric:
>> Thanks for the pointer. I'll hardcode my database paths for now.
Hamish:
> see the db.connect help page example for DBF (I usually just cut and
> paste that to the command line when needed). It accepts variable
> LOCATION, MAPSET, you don't need to hardcode it. (Be sure to keep the
>
Eric:
>> Thanks for the pointer. I'll hardcode my database paths for now.
Hamish:
> see the db.connect help page example for DBF (I usually just cut and
> paste that to the command line when needed). It accepts variable
> LOCATION, MAPSET, you don't need to hardcode it. (Be sure to keep the
> pat
> Eric:
> >> Thanks for the pointer. I'll hardcode my database paths for now.
>
> Hamish:
> > see the db.connect help page example for DBF (I usually just cut
> > and paste that to the command line when needed). It accepts
> > variable LOCATION, MAPSET, you don't need to hardcode it. (Be sure
> >
Patton, Eric wrote:
> > see the db.connect help page example for DBF (I usually just cut and
> > paste that to the command line when needed). It accepts variable
> > LOCATION, MAPSET, you don't need to hardcode it. (Be sure to keep the
> > path with $VARIABLES in single quotes!)
>
> Should each
