Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] demo location uses a hard-coded path instead of GISDBASE? #1419

Closed
infrastation opened this issue Mar 3, 2021 · 1 comment
Closed
Labels
bug Something isn't working

Comments

@infrastation
Copy link
Contributor

Describe the bug
The GUI disregards an existing non-default database directory when automatically creating and activating a demo location.

To Reproduce

  1. install GRASS from the master branch one or two months ago (it could be related to commit 28876fe)
  2. configure a non-default GISDBASE in ~/.grass7/rc and fill it with a few locations and layers
  3. exit GRASS, update to the current master branch and start it again
  4. upon start the GUI will create a new database in ~/grassdata with a location named world_latlong_wgs84 and a vector layer, it will also switch to the new mapset

Expected behavior
It would seem more logical to create the demo location in the current database, and to prompt the user before doing so. Perhaps that's how it works when GISDBASE points to the default directory, but when it is different, the behaviour becomes inconsistent.

@infrastation infrastation added the bug Something isn't working label Mar 3, 2021
@lindakarlovska
Copy link
Contributor

Please, see #1400. Here is explained how the suggested startup is gonna look like.
As @HuidaeCho suggested, I will probably make another variable in rc called "default_gisdbase" which could be manually set up by a user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants