<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/debian/rules, branch 1.3_rc2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_rc2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_rc2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-08-12T09:12:00Z</updated>
<entry>
<title>ctest: show test output in case of failures</title>
<updated>2016-08-12T09:12:00Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-08-12T08:45:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ecaae01f31878a70771f75046b3e00173ff397b5'/>
<id>urn:sha1:ecaae01f31878a70771f75046b3e00173ff397b5</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>CMake: Exclude .md5 and .map doxygen files from install</title>
<updated>2016-08-11T17:51:07Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-11T16:09:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=281383ce1b020013737b28d87988bdf477a90477'/>
<id>urn:sha1:281383ce1b020013737b28d87988bdf477a90477</id>
<content type='text'>
This is much better than removing them in debian/rules.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>CMake: Rewrite existing Documentation support and add doxygen</title>
<updated>2016-08-10T14:17:18Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-08T19:53:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=10ec2d23f14cf5d3e4835d9bcb57d0937f803e6a'/>
<id>urn:sha1:10ec2d23f14cf5d3e4835d9bcb57d0937f803e6a</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>CMake: debian: Switch packaging over to CMake and dh 9</title>
<updated>2016-08-06T20:36:02Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-06T19:40:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e825742bbbbe99b99d525a3b34832b25a7396c84'/>
<id>urn:sha1:e825742bbbbe99b99d525a3b34832b25a7396c84</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>eipp: let apt make a plan, not make stuff plane</title>
<updated>2016-06-29T10:17:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-29T07:16:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8e99b22c31eb47d0422e9a69e83dc99bb315ded8'/>
<id>urn:sha1:8e99b22c31eb47d0422e9a69e83dc99bb315ded8</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>eipp: provide the internal planer as an external one</title>
<updated>2016-06-27T09:57:12Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-28T13:40:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f74d99c6a78caafdc6e32d8cb135683b7154795c'/>
<id>urn:sha1:f74d99c6a78caafdc6e32d8cb135683b7154795c</id>
<content type='text'>
Testing the current implementation can benefit from being able to be
feed an EIPP request and produce a fully compliant response. It is also
a great test for EIPP in general.
</content>
</entry>
<entry>
<title>move 'dump' solver from apt-utils to apt package</title>
<updated>2016-06-08T11:07:21Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-07T18:08:27Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ab07af708e49c9219940ffd3e20a01c763267e03'/>
<id>urn:sha1:ab07af708e49c9219940ffd3e20a01c763267e03</id>
<content type='text'>
</content>
</entry>
<entry>
<title>use *.docs files instead of hardcoding in debian/rules</title>
<updated>2016-05-25T06:32:01Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-25T06:32:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=cb6020cdfea3d6dec6f6ad13843ab46f0c10d562'/>
<id>urn:sha1:cb6020cdfea3d6dec6f6ad13843ab46f0c10d562</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>remove semi-support for different build-dirs</title>
<updated>2016-05-25T06:27:58Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-25T06:27:58Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a97127c3d019ee073c078dbb652a12386f58515b'/>
<id>urn:sha1:a97127c3d019ee073c078dbb652a12386f58515b</id>
<content type='text'>
The debian/rules file tries to guess in which directory it is supposed
to be building, but that guess is always ./build – if it wasn't it
would fail later as not all rules take alternatives into acount.

So, as this is clearly not used lets remove this complexity instead of
fixing it up.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>override lintian on doxygens embedded-javascript-library</title>
<updated>2016-05-24T09:06:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-24T07:55:49Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=83defe877fad2684179d9ddb6e2a40857c3a89e9'/>
<id>urn:sha1:83defe877fad2684179d9ddb6e2a40857c3a89e9</id>
<content type='text'>
The embedding is done completely automatic by doxygen and documented to
be that way for reasons: /usr/share/doc/doxygen/README.jquery

As we can't do anything about it, it is pointless to keep the warning.
</content>
</entry>
</feed>
