plan to use repository-dist in general (whonix and kicksecure)?
Seems possible. If you see the code, only 2 domains lines have to be altered, or even, --domain [whonix|kicksecure|debian|qubes] in the future, and the domains clear and onion will be chosen by this option. But lets start with kicksecure first to avoid dpkg conflicts as you said.
So whonix option to be enabled on kicksecure will be disabled?
The way I did on local branch now is:
if --url is not provided then
if whonix is detected, use it
if kicksecure is detected, use it
if none are detected, error out and ask to provide url.
but the above will be supersed if on whonix for example, you run --url kicksecure to manage kicksecure repo in whonix.
Should this be disabled on kicksecure?
deb [signed-by=/usr/share/keyrings/derivative.asc] tor+https://deb.kicksecure.com bullseye main contrib non-free
Whonix will use:
deb [signed-by=/usr/share/keyrings/derivative.asc] tor+https://deb.kicksecure.com bullseye main contrib non-free
deb [signed-by=/usr/share/keyrings/derivative.asc] tor+https://deb.whonix.org bullseye main contrib non-free
I’ll reset to plain-tls-tor default for now.
Whonix previously was onion by default (all repositories, Debian and Whonix). That however was too unstable back then. Now with onion v3 however it might be worth to do another attempt. I plan on doing this after the next stable point release which should follow in a few days.