From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <446D3D1A.1040003@Sun.COM> Date: Thu, 18 May 2006 22:35:54 -0500 From: Norm Jacobs MIME-Version: 1.0 Subject: Re: [Desktop_printing] Re: [Printing-architecture] Re: Building PAPI implementation References: <446B24E3.2080702@gmx.net> <446B3404.9060809@Sun.COM> <446B8F9E.5070306@gmx.net> <446C42EB.4020709@gmx.net> <446C92C3.8010008@gmx.net> <446CC4D4.10908@Sun.COM> <446CE626.3030901@gmx.net> <446CF46A.8040607@gmx.net> In-Reply-To: <446CF46A.8040607@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Till Kamppeter Cc: printing-architecture , "desktop_printing@osdl.org" 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