Em Qui, 2005-01-06 Ãs 23:39 -0500, Hubert Chan escreveu:
> Which is sort of stupid, because if you have cupsys-bsd installed, you
> get /usr/bin/lpr too. And someone could make /etc/alternatives/print
> point to that. There must be some better way of detecting which system
> is being used. e.g.
>>>>> "Gustavo" == Gustavo Noronha Silva <[EMAIL PROTECTED]> writes:
[...]
Gustavo> Having seen the code for the beast, I don't know if it does the
Gustavo> Right Thing. It uses the 'print' alternative to find out what
Gustavo> spooli
> point to the command used to print (ex.: /usr/bin/lpr)
> Most of the packages conflict with each other and supply lpr and other
> similiar binaries. You probably need to go and check what the
> configuration thing actually needs.
Having seen the code for the beast, I don't know
On Mon, Jan 03, 2005 at 01:05:18AM -0200, Fernanda Giroleti Weiden wrote:
> So, here goes my suggestion and a request: what do you think of using
> the alternatives system for printing?
We could do. I'm not sure how it would all work together though,
alternatives work fine with binaries but with da
Fernanda Giroleti Weiden wrote:
That would ease porting this application to run on Debian. This
application would add a great facility for our users since it is
impossible to know what command must be used to print a document on a
Debian system.
Which ones don't support 'lpr' ? The LPR varients obv
Hi,
I'm packaging the Printer Configuration Tool (default printer config
tool on RedHat/Fedora systems) for Debian. This aplication allows users
to configure printers without needing to know if they're running CUPS,
LPRng or whatever. To do that, the RedHat/Fedora team is using the
alternatives sys
6 matches
Mail list logo
