From: Norm Jacobs <Norm.Jacobs@Sun.COM>
To: Till Kamppeter <till.kamppeter@gmx.net>
Cc: printing-architecture <printing-architecture@freestandards.org>,
"desktop_printing@osdl.org" <desktop_printing@osdl.org>
Subject: Re: [Desktop_printing] Re: [Printing-architecture] Re: Building PAPI implementation
Date: Thu, 18 May 2006 22:35:54 -0500 [thread overview]
Message-ID: <446D3D1A.1040003@Sun.COM> (raw)
In-Reply-To: <446CF46A.8040607@gmx.net>
Till Kamppeter wrote:
> I tried the trick with the links. I did
>
> -------------------------------------------------------------------------
> [root@majax c]# mv /usr/lib/libpapi.so.0.0.0 /usr/lib/libpapi.so.0.0.0.orig
> [root@majax c]# ln -s /usr/lib/psm-ipp.so /usr/lib/libpapi.so.0.0.0
> -------------------------------------------------------------------------
>
> And then I got a lot of output with "printer-query", all CUPS-specific
> options and settings, but still one important thing missing: The options
> in the PPD file. So I cannot build a complete printing dialog with the
> info which I can poll with PAPI and this is very important for the
> standard to be adopted.
>
The PPD file data via a capabilities interface is something that Wendy
is working on. I don't know that there is an ETA yet.
> Another thing is taht if I have queues which are broadcasted from remote
> machines to my local CUPS daemon, "printer-query" cannot poll info about
> them at all. It tells that these queues do not exist.
>
The PAPI implementation in psm-ipp.so will contact the IPP server
that is either the "default" compiled in service, specified via environment
variable (IPP_SERVER, CUPS_SERVER) or via the destination name. Eg.
papiPrinterQuery(svc, "ipp://server/printers/queue", ...);
$ lpstat -p ipp://server/printers/queue -l 2
Part of the attraction of the libpapi-dynamic implementation is that it will
enumerate print queues from a configuration db/name service and resolve
names to uri's on a variety of print services across multiple hosts. To
solve
the update problem with CUPS browse protocol, I prototyped a CUPS browse
listener that can be run to keep /etc/printers.conf up to date. The right
way to do this on systems with CUPS running would be to have CUPS make
the configuration updates via the "PrintcapFormat" directive. I can supply
diffs for this as well. I run both Solaris LP and CUPS on my laptop
side by side
with a mod for this.
> Printing with the PAPI "lpr" command works, but "print-test" complains
> with the following error:
>
> -------------------------------------------------------------------------
> [root@majax c]# print-test -d LJ4050
> print-test: relocation error: print-test: symbol papiJobCreate, version
> SUNWprivate_1.0 not defined in file libpapi.so.0 with link time reference
> [root@majax c]#
> -------------------------------------------------------------------------
>
>
I will look into this.
-Norm
next prev parent reply other threads:[~2006-05-19 3:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 13:28 [Printing-architecture] Building PAPI implementation Till Kamppeter
2006-05-17 14:32 ` [Printing-architecture] " Norm Jacobs
2006-05-17 21:03 ` Till Kamppeter
2006-05-18 9:48 ` [Desktop_printing] " Till Kamppeter
2006-05-18 15:29 ` Till Kamppeter
2006-05-18 19:02 ` Norm Jacobs
2006-05-18 21:24 ` Till Kamppeter
2006-05-18 22:25 ` Till Kamppeter
2006-05-19 3:35 ` Norm Jacobs [this message]
2006-05-19 9:38 ` Till Kamppeter
2006-05-19 12:13 ` Norm Jacobs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=446D3D1A.1040003@Sun.COM \
--to=norm.jacobs@sun.com \
--cc=desktop_printing@osdl.org \
--cc=printing-architecture@freestandards.org \
--cc=till.kamppeter@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.