apt/cmdline/apt-internal-solver.cc, branch 1.3.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.3.12016-06-08T11:07:21Zedsp: optionally store a compressed copy of the last scenario2016-06-08T11:07:21ZDavid Kalnischkiesdavid@kalnischkies.de2016-06-07T15:01:33Zurn:sha1:385d9f2f23057bc5808b5e013e77ba16d1c94da4
For bugreports and co it could be handy to have the scenario and all the
settings used in it around later for inspection for EDSP like protocols.
EDSP might not be the most interesting as the user can still interrupt
the process before the solution is applied and users tend to have an
opinion on the "rightness" of a solution, so it is disabled by default.
edsp: use a stanza based interface for solution writing2016-06-04T17:53:54ZDavid Kalnischkiesdavid@kalnischkies.de2016-06-04T17:53:54Zurn:sha1:71608330b9b2bd95a0481ca53cd58b584fd61e42
EDSP had a WriteSolution method to write out the entire solution based
on the inspection of a given pkgDepCache, but that is rather inflexible
both for EDSP itself and for other EDSP like-protocols. It seems better
to use a smaller scope in printing just a single stanza based on a given
version as there is more reuse potential.
look into the right textdomain for apt-utils again2016-05-28T16:12:02ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-28T11:53:09Zurn:sha1:570ec96dbf4f720d8eff694f8c4429e0b0a033b4
Broken in e7e10e47476606e3b2274cf66b1e8ea74b236757 by looking always
into "apt" while we ship some tools in "apt-utils"…
edsp: use a limited scenario based on bool-array2016-05-20T12:18:36ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-06T14:46:51Zurn:sha1:6dcae298f972eb20223838f0e1dc376c44bc9cc3
Its more space and runtime efficient to use a boolean set instead of a
CacheSet-based implementation.
Git-Dch: Ignore
edsp: add Forbid-{New-Install,Remove} and Upgrade-All2016-05-20T12:18:36ZDavid Kalnischkiesdavid@kalnischkies.de2016-05-06T12:21:02Zurn:sha1:43c71fad3a51d841132ba15a7a5930e1ee4126ed
This allows to differentiate properly between 'apt-get upgrade', 'apt
upgrade' and 'apt full-upgrade'.
convert EDSP to be based on FileFd instead of FILE*2016-05-20T12:18:36ZDavid Kalnischkiesdavid@kalnischkies.de2016-04-26T10:26:12Zurn:sha1:ef00bd7af5b2bc0625df58482eacb4c2873c3647
I doubt there is any non-src:apt usage of these interfaces.
apt-internal-solver: Make ShowHelp() and GetCommands() static2015-12-11T14:01:16ZJulian Andres Klodejak@debian.org2015-12-11T14:00:17Zurn:sha1:9596cb945aee8ab78f37b925e0691a7cc1488d56
This fixes a warning reported by gcc.
Gbp-Dch: ignore
use function pointers instead of weak symbols for cmdline parsing2015-11-29T12:12:38ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-29T12:12:38Zurn:sha1:90986d4dbbd38e2e89f986d621e301304210452e
Passing function pointers around while working on this was very icky,
but if weak symbols are too much to ask for…
Reverts "do not use "-Wl,-Bsymbolic-functions" during the build to avoid
breakage" aka a5fc9be36211a290a7abc3ca2a8bf98943bc1f57.
review of new/changed translatable program strings2015-11-21T17:04:29ZJustin B Ryejustin.byam.rye@gmail.com2015-11-21T16:50:06Zurn:sha1:d04e44ac8177fc5b70ae0189bb5e437c2502f910
Reference mail:
https://lists.debian.org/debian-l10n-english/2015/11/msg00006.html
revamp all tools help messages2015-11-04T17:04:05ZDavid Kalnischkiesdavid@kalnischkies.de2015-10-27T08:57:26Zurn:sha1:8561c2fedae26aecd8ba758a5e7ef686ba1243f3
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.