Bug#627508: conflicting binary path for dconf and d-conf
Kai Lüke
kailueke at riseup.net
Fri Sep 14 19:28:22 UTC 2012
As far as only one file is causing the conflict, I think we would have a
possible solution without renaming the whole package.
Because confdumper doesn't start with dconf it might confuse old dconf
users. So what about dconf.py? (Yes, it's ugly.) Or maybe dconfig is better?
But this would also need renaming the "which('dconf')" part and usage
info in the python file as well as the Make file and manpage.
Any complains?
Greetings,
Kai
More information about the pkg-gnome-maintainers
mailing list