[7597] in SIPB bug reports
Re: xscreensaver conflict with default dotfiles
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Jun 16 12:30:23 2000
Message-Id: <200006161630.MAA07483@small-gods.mit.edu>
To: John Hawkinson <jhawk@MIT.EDU>
Cc: bug-sipb@MIT.EDU
In-Reply-To: Your message of "Fri, 16 Jun 2000 12:14:30 EDT."
<200006161614.MAA00777@contents-vnder-pressvre.mit.edu>
Date: Fri, 16 Jun 2000 12:30:17 -0400
From: Greg Hudson <ghudson@MIT.EDU>
jhawk, if you want me to take your objections seriously, make real
alternative proposals which will satisfy the constraints. You are the
one who pushed fuzzballs to decide to turn the screensaver on by
default. As the developer who has to implement your proposal while
avoiding catastrophes, I find it highly obnoxious that you've objected
to my proposed implementation because it's not perfect, but have not
presented a better solution.
>> As a separate matter, we're finding that having renamed
>> xscreensaver to xss makes gnome kind of unhappy, and we'd like to
>> take the xscreensaver name in 8.5 or so.
> Could you expand more on that?
gnome wants jwz's xscreensaver to be installed, and expects it to be
named "xscreensaver." This is hardcoded in many places, leading to a
raft of local hacks we have to make to gnome to get it to work
properly.
I don't expect we'd ever desupport the xss names.
> Additionally, most users who run "xscreensaver" from their dotfiles
> run it with options that are incompatible with those of "xss". Do
> you have a proposal to address that?
Perhaps you failed to notice the "in 8.5 or so." If xscreensaver
hasn't been the SIPB xscreensaver for over a year, then the number of
users with that dotfile problem is likely to be small.
> So xss-button is not being renamed to xscreensaver-button?
Not for 8.4, certainly.
> I don't see a discussion of this in the fuzzballs discuss meeting.
I don't attend fuzzballs any more. I was informed by either wdc or
jweiss in release-team that fuzzballs had decided to approve your
idea. fuzzballs did not decide on an implementation; that's the
release team's domain.
