Bug#173803: ITP: WvPrint -- Printing System for Linux that makes installing printers truly plug and play

[Patrick Patterson <ppatters@nit.ca>]

On Tuesday 24 December 2002 16:06, Marcelo E. Magallon wrote:
<snip>

>  > (it goes without saying that it handles queuing, and job management).
>
>  Uhm?  So, it goes beyond just installing printers?  Does it have its
>  own queuing or is that implemented on top of something else?  For me,
>  CUPS is as close to PnP as I'd ever like such a component to be.  The
>  _killer_ feature of CUPS for me is the no-nonsense approach to printer
>  management.  I _love_ being able to have the configuration for all the
>  printers in the department in a single place, all the print queues
>  available at a single point and adding clients by just rsync'ing two
>  files to them.
>
How about if we make it as easy as installing WvPrint, and putting two lines 
in the client config file, that point to a "master" server, and each change 
won't even need sync'ing up. ;) (we're even working on getting rid of this, 
but that won't come for a bit... ultimately, we want installing printers to 
be a simple "apt-get install wvprint", and it will let you print to 
everything on the network, that hasn't specifically been deemed "no public 
access".

>  Having something that allows me to say "look for a printer at this
>  address" and have it automagically added to the CUPS configuration
>  would be (welcomed) candy.
>
How about just plug the printer in either to a computer running WvPrint, or 
into the network with a Jet Direct card, and it will be set up ;)

>  > And since this is being written in the same manner that WvDial was,
>
>  Oh, that's why the Wv prefix rang a bell...  the one thing I hate about
>  WvDial is that it was either hard or impossible to integrate it with
>  the rest of the system.  I figure printing on Unix has more historical
>  baggage and it's harder to ignore it (e.g., most programs will expect a
>  System V or BSD-like interface for job submission).

We'll have lp* so that programs that use those won't be confuzzled ;)...

BTW - what do you mean by "hard to integrate with the rest of the system" ??

-- 
Patrick Patterson
Open Source Ambassador
Net Integration Technologies