releng/alpha - Release engineering for Cryptech Alpha board

Age	Commit message (Collapse)	Author
2017-05-11	Fix --conflicts inconsistency between build scripts and Makefile.	Rob Austein
	scripts/build-*.py were treating --conflicts as a sequence of arguments while Makefile was treating as a single argument whose value might contain whitespace. No big deal either way for the scripts, and Makefile is complicated enough, so go with Makefile's approach. Add some pedantic quoting to Makefile while we're at this, out of general paranoia and because the inconsistencies were puzzling.
2017-04-14	Update Debian package dependencies.	Rob Austein
	No longer depends on sqlite3. Does now depend on python-tornado: on some platforms (Debian Jessie) this may need to come from backports.
2017-04-14	Might work better if we were to write emit Python.	Rob Austein

2017-04-14	First cut at a setup.py for our Python code.	Rob Austein

2016-12-14	Oops, need to generate right binary package name too.	Rob Austein

2016-12-14	Support multiple packages corresponding to multiple releng branches.	Rob Austein
	We want to be able to provide packaged builds of development branches. The most straightforward way to do this is a 1:1 correspondence between branches in the releng tree and variant package names. We adopt a simple convention: the base package name corresponds to the master branch, all other branches are named with the base package name followed by the branch name. So the master branch is the cryptech-alpha package, the ksng branch is the cryptech-alpha-ksng branch, and so forth. This isn't a perfect solution, but it's probably good enough. In order to do this, we need to generate the debian/control file at build-time, so that we can generate the list of conflicting packages. This commit also pulls in a few changes that had collected on the master branches of various repositories, chiefly because a few of them were necessary to get it the build to run at all.