[Printing-architecture] PAPI is part of Mandriva Linux now!

Till Kamppeter till.kamppeter at gmx.net
Thu May 18 11:00:42 PDT 2006


today I have finished a first RPM package of PAPI and have already blown
it into Mandriva's Cooker:


So our Cooker is now PAPI-compliant. The RPM is split up into several
binary RPMs. To make the installed Cooker PAPI compliant for users it is
enough to install the libpapi0 and papi-psm packages and to develop
applications accessing the printing infrastructure via PAPI, one has to
install the libpapi0-devel package in addition. The papi-doc package
contains the PAPI specs and additional documentation.

Overview of binary packages:

libpapi0:       The dynamic library which provides the PAPI
libpapi0-devel: The header files for and static libraries for libpapi
papi-psm:       The plug-ins to interface libpapi with CUPS/IPP and LPD
papi-doc:       PAPI specs (PDF), docs for this implementation, source
                code of the sample tools in papi-utils
papi-utils:     Some sample tools using PAPI. Try out PAPI with them and
                study there source code in papi-doc
papi-commands:  BSD and SystemV standard printing commands using PAPI,
                with complete set of man pages. You can switch between
                these commands and the commands supplied by CUPS using
                the "update-alternatives" command. The man pages are
                switched simultaneously.
ruby-papi:      Ruby bindings to allow writing Ruby programs with
                printing functionality.

The source code for these RPMs is the subversion snapshot rev 164 from
http://openprinting.sourceforge.net/. I did not succeed to compile the
(well older) beta1 release on Madriva. Of the current snapshot I
succeeded to build everything except the Apache IPP Module (which does
also not make much sense on a CUPS-eequipped Linux distribution.

I want to ask all of you who work for a Linux distribution (or a Unix in
general) to also package PAPI for your distribution and put it into the
repository which goes towards the next release of the distribution. To
make it easier for you to start, I give you all my RPM packages
including the source RPM for download on:


When we all have PAPI in our upcoming products we have much better
chances to get PAPI into LSB 3.2. So it is important to act quickly as
the LSB 3.2 meeting is in the beginning of June (Waldo, you will go there?).


More information about the Printing-architecture mailing list