On Fri, 10 Oct 2003, Patrick Powell wrote:
PP> HOWEVER, putting /etc/printcap in /etc/lprng/printcap breaks every
PP> tool that uses the printcap.
PP>
PP> Sooooo.... it should be left in /etc/printcap.
PP>
PP> But you can put all the other stuff in /etc/lpd.
Sure, sure. Just document it in the future so it becomes easier to upgrade
between minor releases. It is nice now when I just do a "gmake install"
and at the end it stops the old lpd, starts the new and uses my old config
files. (Except with .22 then that I had to bug patch first. :])
PP> --with-lpd_printcap_path=PATH path of lpd_printcap (default
\${sysconfdir}/${CONFIG_SUBDIR}/lpd_printca
Exactly what is lpd_printcap for?
PP> Note: Once again the autoconf stuff has changed. Now you do not get
PP> the variables expanded... Sigh...
Welcome to a brave new GNU world where solid, stable products (stable API,
etc) is a foreign word. Just look at GTK/GNOME as scary examples and the
mess of library version requirements that plague all Linux distros, where
you need ten different versions of the same library installed due to API
changes and weird dependencies.
Henrik
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
