* Allow an autobuilder with no access to private key material to create testable packages
* Initial dpkg build - will need helpers installed to work
* Start adding required dpkg helpers
* Tweak package artifact names
* Add a windows 'package' builder
* Ensure prefix path handling deals with current directory change when descending to tools dir
* The tools makefile currently only needs the SBINDIR path to install properly
* Add a macos 'package' builder
* Remove unused configure variables
* Without commit history, some of the automatic version numbering will fail
* Add an rpm builder
* Need to set the env var for the rpm build before we change our working dir
* Allow gpg signing to fail for generating test rpm packages
* Unfortunately the rpm spec file hardcodes some path assumptions, so we need to use hacks to work around them
* Return to the top dir before moving things around
* A small change to make actions re-run the pipeline
* Name this workflow file with a nicer looking name
* packages/debian: remove some autogenerate files from repo
* packages/debian/configure
* packages/debian/debian/n2n.debhelper.log
* packages/debian/debian/n2n.postrm.debhelper
are all autogenerated by autoconf or the deb-helper. So there is no need to keep them
in the repo, as it will cause conflicts.
Signed-off-by: Sven Roederer <devel-sven@geroedel.de>
* packages/debian: rules: use dh_prep in place of deprecated "dh_clean -k"
Signed-off-by: Sven Roederer <devel-sven@geroedel.de>
* packages/debian: also provide example communities.list file
You can now do 'cp edge.conf.sample edge.conf' to create a n2n configuration. If the .conf (for edge and supernode) are present, the service is enabled automatically. This prevents unwanted services to be enabled, and it preserves services activation across updates