dctrl-tools/man, branch master

Install mans

2013-07-10T12:00:55Z

(fr) Documentation translation update

2012-05-05T17:55:12Z

Proofread by Thomas Vincent <4FA5666B.7020306@vinc-net.fr>.

(de) Manpages translation update, closes #671597

2012-05-05T13:02:55Z

POT and PO updates

2012-04-29T18:44:11Z

Runtime: no string changed Manpages: +1 fuzzy, +1 untranslated

grep-dctrl: Allow distributing atom modifiers over a parenthesed predicate.

2012-04-22T19:15:39Z

Signed-off-by: Antti-Juhani Kaijanaho

(de) Manpages translation update, closes #664783

2012-03-20T21:22:32Z

(fr) Runtime and documentation translations update

2012-03-15T22:39:45Z

Proofread by Étienne Gilli .

POT and PO updates

2012-03-06T00:21:42Z

Runtime: +1 untranslated Manpages: +5 fuzzy, +1 untranslated

grep-dctrl.1.cp: Fix indentation.

2011-12-18T19:21:38Z

Signed-off-by: Antti-Juhani Kaijanaho

grep-dctrl: Hardcode default input file names.

2011-12-18T19:12:14Z

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