Comment 1 for bug 1309658
Revision history for this message
| David Kalnischkies (donkult) wrote Re: Invalid comments in debian/apt.conf.autoremove | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
As I implemented this years ago I am obviously biased, but I think not supporting "#" as a comment is a mistake as sources.list and preferences support it and most other config files you come across do comments with '#'. The autokernelremove code was an "external" contribution and it just shows that the default assumption is in fact '#'.
(all apt config files I have on my systems include #-comments btw, and I doubt I am the only one)
We should just document this fact properly instead of reverting support for it…
I wonder more why augeas is parsing our config file (but then again, I have no idea what augeas is). We have the apt-config tool to extract settings as well as python-apt, libapt-perl and libapt proper. Doing it on your own leads to a disaster sooner or later…
(just compare it with sources.list parsers… a simple codesearch reveals that most of them are fundamentally broken even in perfectly documented cases; but in most cases I have no idea why they they try to parse it in the first place…)