|
2 years ago | |
---|---|---|
CAcert | 3 years ago | |
packages@eba242264b | 3 years ago | |
.gitignore | 3 years ago | |
.gitmodules | 3 years ago | |
Makefile | 3 years ago | |
README.md | 3 years ago | |
debug.conf | 3 years ago | |
dependencies_debian_9.sh | 2 years ago | |
dependencies_debuntu_common.sh | 3 years ago | |
dependencies_fedora_27.sh | 3 years ago | |
dependencies_opensuse_42.3.sh | 3 years ago | |
enigmail.genxpi.patch | 3 years ago | |
enigmail_pEpAdapter_extensionRelative.patch | 3 years ago | |
local.conf | 3 years ago | |
pep-json-server-adapter_cstring.patch | 3 years ago | |
pepjsonserveradapter.Makefile.conf.patch | 3 years ago | |
prepareEnigmailTree.sh | 3 years ago | |
release.conf | 3 years ago | |
serve.py | 3 years ago | |
tb_pepmda_serve.sh | 3 years ago | |
test.py | 2 years ago |
this build system has two stages:
We distinct between "well supported linuxes", distributions for that we know they ship supported versions of gnupg and we have a dependencies*.sh script for. The version built on debian generates a pep-distribution that should run on all linux installation with a supported gpg version (only if the build- and target architecture match that is)
start on one of the well-supported Linuxes - packages for linux with basic support are built on debian-9 run dependencies_${ID}_${VERSION_ID}.sh for your distribution as root - this has to be done only when dependencies change.
For each actual build, create a user solely for this purpose. On Debian:
adduser --gecos '' pep-enigmail-build
on fedora the libtool shipped with and used by libetpan is broken, therefore use the system one:
cd libetpan; ln -s `which libtool` libtool
test.py contains a very basic test of the pep-json-server: query its version via json