<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/libapt/commandline_test.cc, branch 1.1_exp15</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.1_exp15</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.1_exp15'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2015-11-04T17:04:05Z</updated>
<entry>
<title>revamp all tools help messages</title>
<updated>2015-11-04T17:04:05Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-10-27T08:57:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8561c2fedae26aecd8ba758a5e7ef686ba1243f3'/>
<id>urn:sha1:8561c2fedae26aecd8ba758a5e7ef686ba1243f3</id>
<content type='text'>
The general idea is: A small paragraph on the tool itself as a
description, a list of the most used (!= all) commands available in the
tool, a remark where to find more information on the tool and its
commands (aka: in the manpage) and finally a common block referring to
even more manpages. In exchange options are completely omitted from the
output as well as deprecated or obscure commands. (Better) Information
about them is available in the manpages anyway and the few options which
were listed before were also the least interesting ones (-o -c -q and co
are hardly of interest for someone totally new looking to find info by
asking for help and anyone with a bit of experience doesn't need this
short list. Those would need a list of options applying to the command
they call, but they are too numerous and command specific to list them
sanely in this context.
</content>
</entry>
<entry>
<title>move apts cmdline helper type into -private</title>
<updated>2015-11-04T17:04:04Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-10-26T10:42:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6079b276a959086ff18302cab752b6d7cfe5ad9f'/>
<id>urn:sha1:6079b276a959086ff18302cab752b6d7cfe5ad9f</id>
<content type='text'>
Its not as simple as I initially thought to abstract this enough to make
it globally usable, so lets not pollute global namespace with this for
now.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>generate commands array after config is loaded</title>
<updated>2015-11-04T17:04:04Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-10-25T22:45:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=011188e3920f21e6883c2dab956b3d4fb4e8cbfa'/>
<id>urn:sha1:011188e3920f21e6883c2dab956b3d4fb4e8cbfa</id>
<content type='text'>
This ensures that location strings loaded from a location specified via
configuration (Dir::Locale) effect the help messages for commands.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>allow options between command and -- on commandline</title>
<updated>2014-09-27T23:32:00Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-09-27T23:25:21Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c4b91cbe7cd24126ead1c3fd4b89ff7069bcc148'/>
<id>urn:sha1:c4b91cbe7cd24126ead1c3fd4b89ff7069bcc148</id>
<content type='text'>
This used to work before we implemented a stricter commandline parser
and e.g. the dd-schroot-cmd command constructs commandlines like this.

Reported-By: Helmut Grohne
</content>
</entry>
<entry>
<title>StringToBool: only act if the entire string is consumed by strtol()</title>
<updated>2014-07-16T12:14:40Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@ubuntu.com</email>
</author>
<published>2014-07-16T11:57:50Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=08be0ca32ad69e9ebf28fe26aa85990700c81cf6'/>
<id>urn:sha1:08be0ca32ad69e9ebf28fe26aa85990700c81cf6</id>
<content type='text'>
StringToBool uses strtol() internally to check if the argument is
a number. This function stops when it does not find any more numbers.
So a string like "0ad" (which is a valid packagename) is interpreted
as a "0". The code now checks that the entire string is consumed
not just a part of it. Thanks to Johannes Schauer for raising this
issue.
</content>
</entry>
<entry>
<title>use Google C++ Testing Framework for libapt tests</title>
<updated>2014-04-16T16:36:14Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-04-16T15:09:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f00832cc273e52a47fb88e49849891b771de4e17'/>
<id>urn:sha1:f00832cc273e52a47fb88e49849891b771de4e17</id>
<content type='text'>
My commit 45df0ad2 from 26. Nov 2009 had a little remark:
"The commit also includes a very very simple testapp."
This was never intended to be permanent, but as usually…

The commit adds the needed make magic to compile gtest statically
as it is required and links it against a small runner. All previous
testcase binaries are reimplemented in gtest and combined in this
runner. While most code is a 1:1 translation some had to be rewritten
like compareversion_test.cc, but the coverage remains the same.
</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>fix segfault with empty LongOpt in --no-* branch</title>
<updated>2012-06-09T20:55:51Z</updated>
<author>
<name>David Kalnischkies</name>
<email>kalnischkies@gmail.com</email>
</author>
<published>2012-06-09T20:55:51Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7a6d9076595b2acc164d6f057f609c96c359ea08'/>
<id>urn:sha1:7a6d9076595b2acc164d6f057f609c96c359ea08</id>
<content type='text'>
</content>
</entry>
<entry>
<title>* apt-pkg/contrib/cmdline.cc:</title>
<updated>2012-06-09T20:49:37Z</updated>
<author>
<name>Daniel Hartwig</name>
<email>mandyke@gmail.com</email>
</author>
<published>2012-06-09T20:49:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ae2be086c6996e6ed02b7d828fdcac38248a964d'/>
<id>urn:sha1:ae2be086c6996e6ed02b7d828fdcac38248a964d</id>
<content type='text'>
  - apply patch from Daniel Hartwig to fix a segfault in case
    the LongOpt is empty (Closes: #676331)
</content>
</entry>
</feed>
