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
* Willi Mann wrote [17.06.12 12:34]:
Any progress on this? This should be a rather simple issue.
My recommendation is to rename the binary of dconf. Maybe the binaries
name could be changed to confdumper?
I think this would be a great proposal but from the Debian Policy:
On Sat, 8 Sep 2012, Ulrich Dangel wrote:
* Willi Mann wrote [17.06.12 12:34]:
Any progress on this? This should be a rather simple issue.
My recommendation is to rename the binary of dconf. Maybe the binaries
name could be changed to confdumper?
I think this would be a great proposal but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
Both the package dconf and d-conf with its binary package dconf-tools
ship a binary with the path /usr/bin/dconf. d-conf is a utility that
originates from gnome, and whose purpose is to manage Desktop
Environment Settings. On the other hand,
4 matches
Mail list logo
