Bug#572485: xscreensaver: should not hardcode screenhacks list

2011-12-06 Thread Jose Luis Rivas
On 12/06/2011 09:26 PM, Martín Ferrari wrote: [...] > 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... > Sure Martín, just send me a

Bug#572485: xscreensaver: should not hardcode screenhacks list

2011-12-06 Thread Jamie Zawinski
> Now, as a maintainer, how I am supposed to add a hack to the list? > Surely not editing a conffile from other package in postinst, as that > is not permitted by the Debian Policy. Is there any other way to do > this? Policy aside, that is how you do it. I don't see another way. If ~user/.xscr

Bug#572485: xscreensaver: should not hardcode screenhacks list

2011-12-06 Thread Jamie Zawinski
It's documented in the man page... If you think it's unclear send me a change. I guess you could just regenerate the programs section of the app-defaults file from the existing XML files if you wanted. Then postinst could run the "rebuild" script you've added to the xscreensaver package. I don

Bug#572485: xscreensaver: should not hardcode screenhacks list

2011-12-06 Thread Martín Ferrari
On Wed, Dec 7, 2011 at 01:48, Jamie Zawinski 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

Bug#572485: xscreensaver: should not hardcode screenhacks list

2011-12-06 Thread Martín Ferrari
>> The configuration dialog only shows screenhacks that are either hardcoded >> inside the xscreensaver binary, or manually entered into ~/.xscreensaver. >> This means there is no easy way to make packages that provide additional >> screenhacks. > No, that's what the /usr/lib/X11/app-defaults/XScr

Bug#572485: xscreensaver: should not hardcode screenhacks list

2010-03-04 Thread Jamie Zawinski
> The configuration dialog only shows screenhacks that are either hardcoded > inside the xscreensaver binary, or manually entered into ~/.xscreensaver. > This means there is no easy way to make packages that provide additional > screenhacks. No, that's what the /usr/lib/X11/app-defaults/XScreenSav

Bug#572485: xscreensaver: should not hardcode screenhacks list

2010-03-04 Thread Lars Stoltenow
Package: xscreensaver Version: 5.10-7 Severity: wishlist The configuration dialog only shows screenhacks that are either hardcoded inside the xscreensaver binary, or manually entered into ~/.xscreensaver. This means there is no easy way to make packages that provide additional screenhacks. Curre