Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3.1 2016-09-02T18:11:13Z 2016-09-02T18:11:13Z Julian Andres Klode jak@debian.org 2016-09-02T18:11:13Z urn:sha1:0789f685c14631f43e2ad2bd2b8444733dd4f00d Normally make just lets every job write its output directly, making the log fairly hard to read with high concurrency. 2016-08-19T22:30:14Z Julian Andres Klode jak@debian.org 2016-08-19T22:25:34Z urn:sha1:99fd3fd5943883d947f2f6cd6a7fd9faf0dcc0bf This workaround is a bit more ugly, but does not use a (somewhat) deprecated debhelper command. Gbp-Dch: ignore 2016-08-19T17:39:09Z Julian Andres Klode jak@debian.org 2016-08-19T17:26:55Z urn:sha1:113eaa29214124652e0605730efe028806624151 debhelper 10 is much nicer with the installation part from a dirty tree, so you can just fix some stuff breaking the install step and then continue building with debuild -b -nc until you have fixed all your stuff. It also has some other advantages, of course, like some bug fixes in shell escaping for maintscript, or systemd helper changes. 2016-08-19T17:20:43Z Julian Andres Klode jak@debian.org 2016-08-19T15:49:29Z urn:sha1:23ecbf33dbcea0025c9a72b8c33f5ffb3e5ae146 This gets rid of the special casing of etc/apt, various example file installations handled by the upstream build system, and of course the directory creation for all dirs created by the upstream build system. 2016-08-18T07:56:37Z Julian Andres Klode jak@debian.org 2016-08-11T23:36:55Z urn:sha1:f23ca86fe037f13f744c588b07e4c9140a534894 On Ubuntu, cmake installs are vendor-specific apt.conf.d snippet, causing the build to fail. 2016-08-12T09:12:00Z David Kalnischkies david@kalnischkies.de 2016-08-12T08:45:45Z urn:sha1:ecaae01f31878a70771f75046b3e00173ff397b5 ctest as run by cmake by default does not show the output of the tests even if the tests failed. In terms of our tests it could be handy to set it always, but unfortunately it seems like cmake doesn't allow it if the internet is to be believed, so lets enable it at least while building packages and on travis. Gbp-Dch: Ignore 2016-08-11T17:51:07Z Julian Andres Klode jak@debian.org 2016-08-11T16:09:39Z urn:sha1:281383ce1b020013737b28d87988bdf477a90477 This is much better than removing them in debian/rules. Gbp-Dch: ignore 2016-08-10T14:17:18Z Julian Andres Klode jak@debian.org 2016-08-08T19:53:46Z urn:sha1:10ec2d23f14cf5d3e4835d9bcb57d0937f803e6a This can now build all documentation. It should also be fairly reusable for other projects, as long as they follow the same naming scheme for the po4a output files and set the PACKAGE_* variables used here. We could have done all translations in a single call to po4a like the makefile based buildsystem does. While that would have made the output slightly nicer, this solution offers a huge performance gain because it can translate the documents in parallel, which also means that the xsltproc stage does not have to wait for all translations to be done first. You might think that the add_custom_command() should list the actual output files as BYPRODUCTS. This is not true however: Because the files are not always generated, Ninja will think missing byproducts mean that the target is out of date - which is not what we want. Finally, also add the missing doxygen support. Note that the packaging script cleans up some md5 and map files created by doxygen, otherwise it is fairly boring. 2016-08-06T20:36:02Z Julian Andres Klode jak@debian.org 2016-08-06T19:40:01Z urn:sha1:e825742bbbbe99b99d525a3b34832b25a7396c84 This new packaging is much easier to read, although the duplication in the install files is a bit annoying. We should probably also get rid of the movefiles for solvers, planners, and https method; but then we have to keep track of which methods exist in the apt package. Another disadvantage is that building only the documentation packages also requires building the code, as there's no way to turn off code building in the project. 2016-06-29T10:17:41Z David Kalnischkies david@kalnischkies.de 2016-06-29T07:16:53Z urn:sha1:8e99b22c31eb47d0422e9a69e83dc99bb315ded8 Julian noticed on IRC that I fall victim to a lovely false friend by calling referring to a 'planer' all the time even through these are machines to e.g. remove splinters from woodwork ("make stuff plane"). The term I meant is written in german in this way (= with a single n) but in english there are two, aka: 'planner'. As that is unreleased code switching all instances without any transitional provisions. Also the reason why its skipped in changelog. Thanks: Julian Andres Klode Gbp-Dch: Ignore