I would like to help getting the "deb/rpm packaging" #129 ticket move forward. Since I don't want to pollute that ticket, I am suggesting a rather huge change here. Let me briefly explain "generic packaging".
Whonix's packages (that mostly contain just scripts, config files and package dependencies) are mostly packaged using "generic packaging". It's about where files are stored, how the makefile works and distribution specific packaging tools.
In short, files in etc/... in root source folder will be installed to /etc/..., files in usr/... will be installed to /usr/... and so forth. This should make renaming, moving files around, packaging, etc. very simple. Packaging of most of Whonix's packages (list) looks very similar.
The makefile, the make-helper.bsh script are the same for any package and other files (such as licensing stuff) look very similar.
This makes packaging and maintenance real simple.
Does that make sense?
We also have a few python packages.
Using that method - using the canonical, standard debhelper dh_python2 way - we are able to produce Debian policy conform .deb packages, that means lintian is reporting zero warnings.
Proposal:
You'd need to move files accordingly. Maybe you want several packages? Such as tuf-shared, tuf-server, tuf-client? In that case, create these three folders in the root of TUF's source folder. (Or alternatively split into three git repositories.) Then inside the tuf-client folder, add tuf-client/etc/, tuf-client/usr/, etc. folders accordingly and move files there. Please have a look at the example repositories above to find out where to best place files.
I'd then do my creating a pull request that adds the generic packaging. Can't promise anything, but I think this should be relatively easy. We could also contact debian-mentors, they got a mailing list and irc channel helping with debian packaging questions.
I would like to help getting the "deb/rpm packaging" #129 ticket move forward. Since I don't want to pollute that ticket, I am suggesting a rather huge change here. Let me briefly explain "generic packaging".
Whonix's packages (that mostly contain just scripts, config files and package dependencies) are mostly packaged using "generic packaging". It's about where files are stored, how the makefile works and distribution specific packaging tools.
In short, files in
etc/...in root source folder will be installed to/etc/..., files inusr/...will be installed to/usr/...and so forth. This should make renaming, moving files around, packaging, etc. very simple. Packaging of most of Whonix's packages (list) looks very similar.The makefile, the make-helper.bsh script are the same for any package and other files (such as licensing stuff) look very similar.
This makes packaging and maintenance real simple.
Does that make sense?
We also have a few python packages.
Using that method - using the canonical, standard
debhelperdh_python2way - we are able to produce Debian policy conform.debpackages, that meanslintianis reporting zero warnings.Proposal:
You'd need to move files accordingly. Maybe you want several packages? Such as
tuf-shared,tuf-server,tuf-client? In that case, create these three folders in the root of TUF's source folder. (Or alternatively split into three git repositories.) Then inside thetuf-clientfolder, addtuf-client/etc/,tuf-client/usr/, etc. folders accordingly and move files there. Please have a look at the example repositories above to find out where to best place files.I'd then do my creating a pull request that adds the generic packaging. Can't promise anything, but I think this should be relatively easy. We could also contact debian-mentors, they got a mailing list and irc channel helping with debian packaging questions.