I recommend the distribution of binaries at the very least along with SHA256 or BLAKE2b (ideally the latter) checksums to check for the files’ integrity. It took me quite some time to build it using cargo on my system because it ran into a couple of issues regarding missing libraries and whatever else I already forgot AT THE END OF THE COMPILATION OF ALL ~308 dependencies, i.e. at the linking phase. On top of that, I have a hard drive and a horrid, extremely slow desktop PC. If you would like to, you could use torrent files (in addition, perhaps?), I would offer seeding the files.
Of course it should not include the binaries alone, but the manual pages and so forth. The whole proper hierarchy, say: bin/, include/, share/man/ and whatever else one (or pijul) may need. Perhaps an example configuration file with comments?
What I would recommend heavily against is distributing pijul on Snap EXCLUSIVELY. Snap is Canonical’s own walled garden. If you were to distribute a .deb file, at least one could simply extract the files and run the executable without any issues. If there are concerns with regarding to sandboxing, that is not up to the maintainers of pijul to handle, but they may recommend firejail on Linux, and even write a firejail profile if it is that important.
I am not sure if pijul works under OpenBSD or DragonflyBSD, but I am willing to port it if it does not work, but only as so far as it does not seem like a time-consuming task ask I have a zillion of things to do already.
Hello.
I recommend the distribution of binaries at the very least along with
SHA256orBLAKE2b(ideally the latter) checksums to check for the files’ integrity. It took me quite some time to build it usingcargoon my system because it ran into a couple of issues regarding missing libraries and whatever else I already forgot AT THE END OF THE COMPILATION OF ALL ~308 dependencies, i.e. at the linking phase. On top of that, I have a hard drive and a horrid, extremely slow desktop PC. If you would like to, you could use torrent files (in addition, perhaps?), I would offer seeding the files.Of course it should not include the binaries alone, but the manual pages and so forth. The whole proper hierarchy, say:
bin/,include/,share/man/and whatever else one (orpijul) may need. Perhaps an example configuration file with comments?What I would recommend heavily against is distributing
pijulonSnapEXCLUSIVELY.Snapis Canonical’s own walled garden. If you were to distribute a.debfile, at least one could simply extract the files and run the executable without any issues. If there are concerns with regarding to sandboxing, that is not up to the maintainers ofpijulto handle, but they may recommendfirejailon Linux, and even write afirejailprofile if it is that important.I am not sure if
pijulworks underOpenBSDorDragonflyBSD, but I am willing to port it if it does not work, but only as so far as it does not seem like a time-consuming task ask I have a zillion of things to do already.