| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Until now, grep-dctrl has used a configuration file to determine which
input file it should use by default. Originally, this was motivated by
a desire not to step too much into the toes of dpkg maintainers - it
allowed the fiction that this package doesn't in fact depend on dpkg's
internal interfaces. Over the last decade, however, this consideration
has became essentially moot, and the status and available files are
effectively public interfaces.
Now, theoretically, this configurability could be in use by someone.
However, the same functionality is available by using shell functions and
shell scripts. I twice called for actual use cases for this feature,
explicitly threatening to remove this feature if nobody stepped up.
Nobody did.
Signed-off-by: Antti-Juhani Kaijanaho <ajk@debian.org>
|
|
<20111208103543.GA24436@xibalba.demon.co.uk>
|
|
|
|
Signed-off-by: Antti-Juhani Kaijanaho <ajk@debian.org>
|
|
There are some places in the code where it would simplify both the code
and the translations to have message strings be printf-formatted. This
change changes the message function interfaces so that they can take
a variable number of arguments. This required changes at all call sites.
At the same time, the key logic of the message functions is moved out of
the headers, leaving only the "shall we output this" test for inlining.
Signed-off-by: Antti-Juhani Kaijanaho <ajk@debian.org>
|
|
Signed-off-by: Antti-Juhani Kaijanaho <ajk@debian.org>
|
|
|
|
|
