aboutsummaryrefslogtreecommitdiff
path: root/scripts
AgeCommit message (Collapse)Author
2017-05-20Better Homebrew fix: Just symlink our bindings into our vendor tree.Rob Austein
Homebrew reserves the right to decide on the fly which copy of the Python 2.7 interpreter (Apple's or Homebrew's) we should be using. This is mostly reasonable, but makes it tricky when a Homebrew package includes both a Python "application" and Python "bindings", because the bindings may be installed where the script doesn't see them. So we symlink the bindings into the application's private library tree, just as if the bindings were a third-party library our application needed. Silly, but it works (this week).
2017-05-20Scripts need to use same version of Python as libraries.Rob Austein
2017-05-11Fix --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-05-10Homebrew wants transitive closure of our Python dependencies.Rob Austein
2017-04-15Update Homebrew formula.Rob Austein
* Drop dependency on SQLite3; * Add dependency on Tornado; * Use setup.py to install our own Python code; * Document the Python voodoo better, well, differently.
2017-04-14Update 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-14Might work better if we were to write emit Python.Rob Austein
2017-04-14First cut at a setup.py for our Python code.Rob Austein
2016-12-14Fix Homebrew formula class name.Rob Austein
Apparently Homebrew expects the formula class name to match the name of the recipe, and gets tetchy when they do not. Minimal fix, wires in assumptions about how we punctuate package names, but simple and should suffice for now. While we were at this, changed argument parsing for build-homebrew-formula.py to use named (--foo) rather than positional arguments.
2016-12-14Minor tweaks to branch-based package conflict hacks.Rob Austein
Get conflict indentation right in generated Homebrew formula. Consider remote branches as well as local ones when constructing conflict list, so that we don't omit a conflicting package just because we've never checked it out in this build tree.
2016-12-14Oops, need to generate right binary package name too.Rob Austein
2016-12-14Support 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.