apt/buildlib, branch 1.1.exp1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.exp12014-04-13T20:12:01Zcompile with absolute paths to allow lcov use2014-04-13T20:12:01ZDavid Kalnischkiesdavid@kalnischkies.de2014-04-13T19:40:35Zurn:sha1:cbc9ec23b0fb551f20f4fd8ca46d98f59b5666bc
Instructing gcc (or clang) to prepare for capturing coverage data is
easy: Just build with: CXXFLAGS=--coverage
The hard part is that our buildsystem uses relative paths and so
confuses the hell out of lcov as it assumes this way that all our *.cc
files are in the same directory… by changing to absolute paths in the
compile rules we solve this problem.
Still not perfect as it refers to build/include files for most headers
and our forking/threading code isn't properly captured, but good enough
to see red reports for now:
CXXFLAGS=--coverage make
make test
./test/integration/run-tests -q
lcov --no-external --directory . --capture --output-file apt.info
genhtml --output-directory ./coverage/ apt.info
Git-Dch: Ignore
use liblzma-dev to provide xz/lzma support2014-03-13T13:00:38ZDavid Kalnischkiesdavid@kalnischkies.de2014-03-12T13:39:18Zurn:sha1:7f350a377e0c65a656b9b5437e27d037fd742901
We have xz/lzma support for a while, but only via an external binary
provided by xz-utils. Now that the Debian archive provides xz by default
and dpkg pre-depends on the library provided by liblzma-dev we can switch
now to use this library as well to avoid requiring an external binary.
For now the binary is in a prio:required package, but this might change
in the future.
API wise it is quiet similar to bz2 code expect that it doesn't provide
file I/O methods, so we piece this together on our own.
enable various compiler warnings2014-03-13T12:58:45ZDavid Kalnischkiesdavid@kalnischkies.de2014-03-06T01:36:48Zurn:sha1:9d9d5e810751954594c793383b07ca526c647350
Now that the last few commits resolved the issues we can finally enable
a bunch of compiler warnings by default.
Git-Dch: ignore
cleanup headers and especially #includes everywhere2014-03-13T12:58:45ZDavid Kalnischkiesdavid@kalnischkies.de2014-03-05T21:11:25Zurn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f
Beside being a bit cleaner it hopefully also resolves oddball problems
I have with high levels of parallel jobs.
Git-Dch: Ignore
Reported-By: iwyu (include-what-you-use)
move defines for version to macros.h2014-03-13T12:58:45ZDavid Kalnischkiesdavid@kalnischkies.de2014-03-01T21:27:11Zurn:sha1:54298f49d71347616df19b8d2f59c907374e07b3
also adds namespaced attributes for good usage
Git-Dch: Ignore
Fix typos in documentation (codespell)2014-02-22T17:34:33ZMichael Vogtmvo@debian.org2014-02-22T17:34:33Zurn:sha1:1e3f4083db29bba600b9725e9456b0e140975c99add a vendor specific file to have configurable entities2013-11-30T22:34:15ZDavid Kalnischkieskalnischkies@gmail.com2013-11-30T18:15:02Zurn:sha1:694ef56e802bbab94595fc491fdc6ef8b4f525c1
manpages sometimes refer to distro-specific things like the name of the
package providing the achive-keyring. Having a central place to
configure this helps in having it consistent in the manpages and allows
to load this info from other places in the buildsystem as well later.
* move upgrade releated code into upgrade.{cc,h}2013-10-05T10:15:03ZMichael Vogtmvo@debian.org2013-10-05T10:15:03Zurn:sha1:82e369c4b93b5b81db7988ab377a3c5bd388268e
The upgrade releated code is moved into upgrade.{cc,h} and
all pkg*Upgrade* prototypes are included in algorihms.h to
avoid breaking API (unless build with APT_9_CLEANER_HEADERS).
reenable automatic parallel build of APT2013-07-26T18:37:34ZDavid Kalnischkieskalnischkies@gmail.com2013-07-26T18:37:34Zurn:sha1:0cedc6b3fe775ccb814ee3393d4695909bcc7ece
It works for a while now in manual tests, now lets see how it will
perform if enabled for all by default automatically.
make autoconf happy by "mv configure.{in,ac}"2013-07-26T12:12:29ZDavid Kalnischkieskalnischkies@gmail.com2013-07-26T12:12:29Zurn:sha1:ed9ba607b47feae1a435126c5fa05ac2a3690099
Git-Dch: Ignore