What is the best Whonix workflow

While nothing speaks against it, I don’t think it is usual practice / any useful to rename the origin which in this case is Whonix to anything else. Never saw this practice anywhere. Easier / “better” would be:

git remote add your-github-name git@github.com:YOUR_GITHUB_NAME/Whonix.git
git remote add irykoon git@github.com:YOUR_GITHUB_NAME/Whonix.git

It always makes sense to do that.

Fully optional, to speed up the process, add: --jobs=4

While this forum thread is not about building… Still… Useful from Whonix build documentation…

https://www.whonix.org/wiki/Dev/Build_Documentation/14_full

We suggest the following command to clone all of Whonix’s repositories.

cd; git clone --jobs=4 --recursive https://github.com/Whonix/Whonix

Once one has cloned all of Whonix’s source code, one could use the mygrep. Like changing the name of a variable or when renaming a file, it is useful to grep all the meaningful (that is excluding licenses and git folders etc) Whonix source files for references. That way any interaction between packages could be found.


Not sure if forking Whonix is convenient or if Whonix is doing something it could do better in order to make that process more standardized / simpler.

2 Likes