I hate mailing lists too. Forget the attachments, here's the content. See: http://bugzilla.ximian.com/show_bug.cgi?id=55696 for the attachments talked about here. -------- Forwarded Message -------- > From: Not Zed <notzed ximian com> > To: Anna M Dirks <anna ximian com> > Cc: fejj ximian com, evolution-hackers ximian com > Subject: Re: [Evolution-hackers] Re: lockdown keys > Date: Wed, 17 Mar 2004 14:34:39 +0800 > Mailer: Ximian Evolution 1.5.5 > > Ok here's an updated patch. I've included a screenshot of the new ui to > control how often empty trash on exit is run. This should mean most of > the stuff is done for lockdown ... but it doesn't seem to ... > > ... while trying to test this (Jeff - please, we should be testing every > commit these days ...), i had trouble finding out how to make keys > readonly. > > As far as I can tell, there isn't any such way to do this. > > I tried the .gconf.path stuff with a read-only mirror of the mailer > stuff, but everything is still read-write. I even tried chmod, but that > didn't work (and is too coarse anyway). > > I guess i could've done it wrong too, i just tried copying > ~/.gconf/apps/evolution/mail -> ~/.gconf.ro/apps/evolution/mail (after > setting that path up), and i even tried copying it > to /etc/gconf/gconf.xml-mandatory/apps/evolution/mail (does it use a > different format?). I even tried removing the stuff in > ~/.gconf/apps/evolution/mail, and it just came up like the values didn't > exist. I tried a few other things besides, to make sure i wasn't making > a mistake. > > What did i do wrong? Or did we misunderstand gconf? > > But basically, it looks like we just wasted our time with a big bunch of > code, and we're going to have to move to doing everything via policy > keys and then enforcing the policies in the client code. > > I hate gconf.
Attachment:
empty-trash-exit.png
Description: Binary data