I’m just getting started on learning the Gramps codebase. The Wiki page on running a development version of Gramps says that one way to do it is to run it from the trunk/build directory. (https://gramps-project.org/wiki/index.php/Running_a_development_version_of_Gramps#Option_2:_use_the_build_code) The page makes it sound like the directory should already be there, but I can’t find a directory called trunk. Should I create it? Has the name of the directory changed since the wiki page was updated? Or is there something I’m misunderstanding?
(I’m using Ubuntu 22.04, and I’m currently on the master branch of Gramps, and I’ve already run python3 setup.py build.)
The instructions are pretty old, and because I’m too lazy to maintain them, I tend to follow the instructions in the README and INSTALL files that you can find on GitHub. And even these can be more complex than needed, if you just want to run Gramps from source.
In practical terms this means that after a successfull build, the only command that I run is:
python3 Gramps.py
I often put an ampersand behind that, so that Gramps starts in the background, and I still have the command line available for other things, like installing missing dependencies.
Like Nick wrote, it is created for you, and its standard location is inside your project directory, i.e. inside your cloned repo. You can change that with command options, if you want to, but I’ve never tried that, and never fellt a need to do that either.
And personally, I haven´t the faintest idea why I should use anything else than Option 0, which I would probably call Option 1, when I edit the wiki.
Note that, when you run from source this way, Gramps has full access to the existing config and data. There is a warning about that, but the page gives no directions for alternatives.