[722] in athena10
Re: Printer setup dialog weirdness
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Wed Dec 10 13:49:44 2008
Cc: athena10@mit.edu
Message-Id: <58A7FCC8-B392-4EFA-80FE-3A38D3BEC31A@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Evan Broder <broder@mit.edu>
In-Reply-To: <493FD627.1090008@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: Wed, 10 Dec 2008 13:48:57 -0500
Confirmed. Downloading Dell's PPD files (which was harder than it
needed to be, since apparently only Dell's European site acknowledges
the existence of the 5210n printers we have) and dropping them in /
usr/share/ppd/1-local-admin (which is a symnlink to /usr/local/share/
ppd) works fine. After restarting cups, they show up in the vendor
lists in the "New Printer" wizard.
I'll bring this up at release-team today to figure out a good way of
doing this which does as much as possible to prevent bitrot.
-Jon
On Dec 10, 2008, at 9:45 AM, Evan Broder wrote:
> Jonathan Reed wrote:
>>
>> How easy is it to create a package which adds to the printer driver
>> database? I wonder if we want to create debathena-ppds and ship PPD
>> files for all the common models at MIT (the Dells, for example)
>>
>> -Jon
>>
>
> I just skimmed through a bunch of PPD-providing packages, and it looks
> like we could just drop them in /usr/share/ppd/debathena/ or something
> like that. That being said, I know nothing at all about how PPD
> files fork.
>
> - Evan
