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…)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309658

Title:
  Invalid comments in debian/apt.conf.autoremove

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1309658/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to