<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg/aptconfiguration.cc, branch 1.1.exp11</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.1.exp11</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.1.exp11'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2015-08-17T10:01:45Z</updated>
<entry>
<title>Cleanup includes after running iwyu</title>
<updated>2015-08-17T10:01:45Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@debian.org</email>
</author>
<published>2015-08-17T10:01:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=88a8975f156e452d9f3ebe76822b236e8962ebba'/>
<id>urn:sha1:88a8975f156e452d9f3ebe76822b236e8962ebba</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make apt compile with clang++ again</title>
<updated>2015-08-14T17:44:25Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@debian.org</email>
</author>
<published>2015-08-14T17:44:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f8043f219f077b1cfc6c5ad2263c4caa4709a00d'/>
<id>urn:sha1:f8043f219f077b1cfc6c5ad2263c4caa4709a00d</id>
<content type='text'>
This allows us to run the clang static analyzer and to run the
testsuite with the clang MemorySanitizer.
</content>
</entry>
<entry>
<title>mark private methods as hidden</title>
<updated>2014-09-29T22:15:15Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-09-29T13:41:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3809194b662f48733916e6248cd0c141f281313d'/>
<id>urn:sha1:3809194b662f48733916e6248cd0c141f281313d</id>
<content type='text'>
We are the only possible users of private methods, so we are also the
only users who can potentially export them via using them in inline
methods. The point is: We don't need these symbols exported if we don't
do this, so marking them as hidden removes some methods from the API
without breaking anything as nobody could have used them.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>invalid cache if architecture set doesn't match</title>
<updated>2014-05-10T10:50:00Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-05-10T10:50:00Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7a223b933cab0447438ca2e964576da39078eaf4'/>
<id>urn:sha1:7a223b933cab0447438ca2e964576da39078eaf4</id>
<content type='text'>
The cache heavily depends on the architecture(s) it is build for,
especially if you move from single- to multiarch. Adding a new
architecture to dpkg therefore has to be detected and must invalidate
the cache so that we don't operate on incorrect data.

The incorrect data will prevent us from doing otherwise sensible
actions (it doesn't allow bad things to happen) and the recovery is
simple and automatic in most cases, so this hides pretty well and is
also not as serious as it might sound at first.

Closes: 745036
</content>
</entry>
<entry>
<title>do not create an (additional) empty compressor</title>
<updated>2014-04-11T09:16:04Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-04-11T09:16:04Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8056a00cd76c0f9dd6c444f23aa9998f96f805ed'/>
<id>urn:sha1:8056a00cd76c0f9dd6c444f23aa9998f96f805ed</id>
<content type='text'>
FileFd code knows how to deal with such a compressor, so it isn't a
problem, but it is absolutely not needed as we already have an
(matching) identity compressor with '.' earlier in the list.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>use liblzma-dev to provide xz/lzma support</title>
<updated>2014-03-13T13:00:38Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-03-12T13:39:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7f350a377e0c65a656b9b5437e27d037fd742901'/>
<id>urn:sha1:7f350a377e0c65a656b9b5437e27d037fd742901</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>cleanup headers and especially #includes everywhere</title>
<updated>2014-03-13T12:58:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-03-05T21:11:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=453b82a388013e522b3a1b9fcd6ed0810dab1f4f'/>
<id>urn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f</id>
<content type='text'>
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)
</content>
</entry>
<entry>
<title>warning: type qualifiers ignored on function return type [-Wignored-qualifiers]</title>
<updated>2014-03-13T12:58:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-03-01T12:55:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d64e130aa333837a8fda0f1bba51f2867ca520f7'/>
<id>urn:sha1:d64e130aa333837a8fda0f1bba51f2867ca520f7</id>
<content type='text'>
Reported-By: gcc -Wignored-qualifiers
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>support DEB_BUILD_PROFILES and -P for build profiles</title>
<updated>2014-03-13T12:58:44Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-02-25T13:26:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ce7f128c020e1347f91c6074238fc5da58c5df71'/>
<id>urn:sha1:ce7f128c020e1347f91c6074238fc5da58c5df71</id>
<content type='text'>
Inspired by the rest of the patch in 661537, but abstract the
parsing of various ways of setting the build profiles more so it can
potentially be reused and all apt parts have the same behaviour.

Especially config options, cmdline options and environment will not be
combined as proposed as this isn't APTs usual behaviour and dpkg doesn't
do it either, so one overrides the other as it normally does.
</content>
</entry>
<entry>
<title>add default and override handling for Cnf::FindVector</title>
<updated>2014-03-13T12:57:34Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-02-24T22:10:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a5414e56403537678d5be87acf59c37a05f55719'/>
<id>urn:sha1:a5414e56403537678d5be87acf59c37a05f55719</id>
<content type='text'>
Automatically handle the override of list options via its parent value
which can even be a comma-separated list of values. It also adds an easy
way of providing a default for the list.
</content>
</entry>
</feed>
