XScreenSaver module API depends on build environment about x11

[dmwit]

I'm happy enough to bump to 1.9 and release. Looks like xmonad (the other big customer) still builds fine assuming you can get X11 built at all with its new dependency, so that's fine; and anyway it has X11<1.9 in its build-depends. Even so, I'm paranoid, so I'm checking in with the xmonad maintainer for objections; if I don't get any in the next three days I'll make a release.

[dmwit]

Released. Thanks for the reminders.

[geekosaur]

FWIW I made the same argument with respect to the Xinerama/XRandR module, and was informed that somehow this logic is incorrect and the current setup is "correct". I still do not understand the claimed justification, and regard it as a bug.

[nomeata]

I keep getting user complaints whose build fails. Can we make a decision how to proceed there? I see these options

• The extension becomes non-optional
• The module moves to its own package.
• None of them, and my program will revert to a embedded copy of the module.

[dmwit]

The extension should be non-optional. Do you want to have commit bit and make it happen? I'll be happy to add you.

[nomeata]

I gave it a shot at #61

[nomeata]

Can we have a release with this fix? My users still face build errors.