Changes

You may also simply do your development as another user, so you won't access your usual <code>~/.gramps </code> database when testing.

You can also create an alias account with the same user and group IDs, but with a different login name and different home directory, typically, a subdir of the real user's home directory. This gives the benefit of less disk usage, and no permission boundary between the two account aliases. On the other hand, if you are afraid of malicious code within gramps purposefully breaking out and wreaking havoc on your real home account's <code>.gramps</code>, this method is too weak for you. For regular development scenario, though, this setup certainly does suffice.

This is what the cloning looks like in my <code>/etc/passwd</code>:

Create symlink to the dotfiles you want to reuse. Obviously, don't do this for ''<code>.gramps</code>''! Something like (inside <code>~vassilii/pub</code>):