- /var/lib/whonix/do_once/whonixsetup.done as whonix-repository-wizard done file
- We also need one for locale_settings_finish?
I am prosing a more generic approach. Here is an example:
Users, custom builders and derivative distributions (Whonix Qubes can be considered a derivative of Whonix) can use that one. whonix-setup-wizard never touches folder for writing. Also not during apt-get purge. Only for reading.
Whonix Qubes does not need/want the disclaimer, so their qubes-whonix package could ship a /var/lib/whonix-setup-wizard/status-files/disclaimer.skip file.
Used by whonix-setup-wizard for status files. Once the user accepted the disclaimer, a file /var/lib/whonix-setup-wizard/status-files/disclaimer.done could be created. And on next run, we can skip the disclaimer wizard page. The /var/cache/whonix-setup-wizard/status-files folder would not be deleted on apt-get remove, but it would be removed on apt-get purge.
We could also stick to the current convention whonix/do_once, since it's a Whonix specific application.
Having this mechanism, we could have a python function, that abstracts checking these two folders for existing status files. So we can run that function and say "if function says, state file exists, skip it, otherwise continue".
The apt-get remove vs purge distinction can very easily be implemented by me in debian/ maintainer scripts.
What do you think?