releng/alpha - Release engineering for Cryptech Alpha board

Age	Commit message (Collapse)	Author
2018-06-17	Packaging voodoo to support same code version on multiple releases.	Rob Austein
	reprepro strictly follows the Debian package rule that two package files which have the same name must have identical content. Which is fine, except when we want to support the same version of a package on multiple releases of the same Debian-flavored operating system. The usual hack for this is to add a release-specific tag to the end of the version string. The brute force way of doing this requires modifying the source package for each release, but there's an obscure hack which lets us augment the binary package versions directly.
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.
2016-08-10	Whole bunch of improvements to Debian packaging from Ondrej Sury (thanks!).	Rob Austein

2016-07-05	Add python-serial to runtime dependencies.	Rob Austein

2016-06-27	First cut at consolidated alpha releng.	Rob Austein
	Undoubtedly doesn't work yet, and still needs doc, but perhaps now ready for testing on build machine.