[6621] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: Desupporting lpr2 in the consult locker

daemon@ATHENA.MIT.EDU (Jonathan Reed)
Sat Feb 13 00:49:10 2010

Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <alpine.DEB.1.10.1002130017280.31485@dr-wily.mit.edu>
Date: Sat, 13 Feb 2010 00:49:01 -0500
Cc: release-team@MIT.EDU, consultdev@MIT.EDU
Message-Id: <A9E9449D-C210-4A83-8620-7D90967AB48B@MIT.EDU>
To: Geoffrey Thomas <geofft@MIT.EDU>
Content-Transfer-Encoding: 8bit


On Feb 13, 2010, at 12:26 AM, Geoffrey Thomas wrote:

> As a random thought, I wonder if it would be better to make it actually print the document (in case this is in dotfiles or your app defaults or something and you're in a hurry to get something printed for class) with a page on top saying in big scary letters "Don't use lpr2! See http://foo". (And still send e-mail.)

Well, another option is to change it ~now to start warning but still print the document.  I'd rather do that than muck with the output -- it's far easier to whine at the user and then just run lpr2.real or something.

Then in, say May we can make it just warn and not print.  

And we can delete it in, say, August.

> Anyway, since I don't like how we litter one-use dotfiles over the top level of the user's home directory, I'm slowly making a vague effort to acknowledge the XDG directory spec [1], which shares the same motivation, and use ~/.config/debathena/foo for new Debathena stuff. I'm not sure if you want to use that (or ~/.config/athena/lpr2-nagged) here.

Noted.  I'd likely use ~/.config/athena since this will apply to not just debathena, but that can be finalized later.

-Jon

home help back first fref pref prev next nref lref last post