[1351] in athena10
Re: the debathena-managed metapackage
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Sat Mar 7 01:28:53 2009
Cc: Evan Broder <broder@mit.edu>, Greg Price <price@mit.edu>,
debathena@mit.edu
Message-Id: <DEA013F0-8490-4DB2-8780-C384440B2ACC@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Tim Abbott <tabbott@mit.edu>
In-Reply-To: <alpine.DEB.2.00.0903061953130.15811@vinegar-pot.mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sat, 7 Mar 2009 01:22:54 -0500
>> I withdraw my previous comment about #1. All athena 9 machines
>> offer the
>> logout option, and per-user customization to disable it. Since a
>> gconf key
>> controls whether the logout option appears or not, perhaps we can
>> do something
>> clever like force the logout option on -cluster, and obey the
>> user's gconf key
>> (if set) on -workstation.
>
> I don't think forcing the gconf key on -cluster users is useful;
> they can
> always run a build of xscreensaver out of their home directory
> instead if
> they want to avoid the logout button.
I assume you meant -workstation, not -cluster, right? (Since we
currently _do_ force cluster users to have a logout button)
Fair enough, I suppose, though ISTR there were objections to this on
zephyr this morning. I'm not sure how many other people know about
the ability to disable the logout button (I didn't even remember until
it was mentioned) or care.
I suppose the other option would be to split out the screensaver
logout thing into its own package and let -workstation users take it
if they want, but then we run the risk of going down the road where we
have a bunch of debathena-miniscule-customization-that-one-person-
objects-to packages, and that will probably suck.
-Jon
