Does Whonix have any example of a Source with multiple Packages that have man pages that need to be installed per package?
Currently, it is installing all man pages for each package. Didn’t find anything searching the web. Just trying to understand how other packages does this.
Im remembering now I already tried to port my manpage generation from pandoc to ronn, but it didn’t work. Tried again, don’t know how to fix.
The manpages are pretty dense on information, so I need to keep them organized and easy to read, and with pandoc is working. If you can port the manuals to ronn without drawbacks then that is ok.
genmkfile manpages is manual when a man page source file was updated (ronn) and the roff needs to be updated. If I remember to do that. Doesn’t seem too useful to automate that during the build process. Would have to check contents are reproducible / deterministic.
Otherwise the build process only automatically takes the files from the autogenerated folder.
So you don’t need to worry about manpages. I generate them with a script before pushing (most of the time hehe).
Just fixing lintian warnings and it is pretty much ready for review and trying to break the scripts.
GW should install onionjuggler-cli onionjuggler-cli-auth
WS should install onionjuggler-cli-web
GW or WS can install onionjuggler-tui, it is quite handy, just not “beautiful” because it has to be versatile to check which onionjuggler-cli commands it has.
Note: anon-apps-config is installed on both workstation and gateway. But
that is good enough. The config snippet itself could check where it’s
running (the usual marker files) and only apply gateway config to
gateway and workstation config to workstation.
Will this be required in the final version as a user action?
No, Im hoping anon-apps-config would do this.
But also, as I don’t plan to ship to debian.org. just whonix for now, then I could do two packages, one for GW and one for WS, then the configuration shipped would be correct
Would you prefer onionjuggler-lib-workstation and onionjuggler-lib-gateway to be created instead of relying on anon-apps-config? Then you should drop the standard onionjuggler-lib that uses the debian.conf as default.
Ah. Yes. A pull request for anon-apps-config would be welcome.
Better keeping the number of packages low. Packages with just only 1 file are best avoided in any case (even rejection reason for packages.debian.org).
configuration files are not intended to run commands
After seeing it will not be done by anon-apps-config, I get back to the point of building two onionjuggler-libs, one for WS and one for GW. Would you accept this?
Can’t be because then I’d need to modify the dependencies of other packages to point to the right lib.
I think the best to be done is two onionjuggler packages, one for gw, one for ws.