On Wed, Dec 7, 2011 at 01:48, Jamie Zawinski <j...@jwz.org> wrote: > If ~user/.xscreensaver lists hacks A, B and C, and you want them to also see > D, you need to put D in the system-wide /.../app-defaults/XScreenSaver file. > > I guess you could modify both packages to install their version as > XScreenSaver-pkgname and then have postinst for both packages treat the > app-defaults file as a generated file from whatever wild carded files it > finds. Maybe that would work as a loophole for whatever the policy is.
The policy has good reasons for that. Although, what you suggest could be a solution, the problem is migrating current configurations where that file has been locally modified. As a side note, I would like to suggest you to document this somewhere in the upstream source, as I think most people will assume that the XML files are enough, and spend a lot of time trying to understand why XScreensaver is not reading them. José, do you think it is possible to implement Jamie's suggestion? There aren't many xscreensaver hacks in the archive, but they will benefit from this, and it would make a lot easier to package new hacks... -- Martín Ferrari -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
