* [Printing-architecture] PAPI RPM implementation for Mandriva's Cooker
@ 2006-06-14 20:52 Till Kamppeter
2006-06-14 21:03 ` Norm Jacobs
0 siblings, 1 reply; 2+ messages in thread
From: Till Kamppeter @ 2006-06-14 20:52 UTC (permalink / raw)
To: printing-architecture, Norm Jacobs, Wendy Phillips
Oi,
in todays architecture telecon we have talked about the implementration
of PAPI in the distros and my PAPI RPMs for Mandriva.
Here you find source and binary RPMs for Mandriva's Cooker and also the
source tarball (SVN rev 171) and the spec file:
http://www.freestandards.org/~till/tmp/papi/
There are no patches, all file manipulation is done with Perl. The
libraries are renamed and selected by update-alternatives (default is
IPP library for CUPS), as libpapi-dynamic does not work very well with
CUPS. This scheme should perhaps be adopted upstream for easier
integration in distros.
You also see the splitting of binary RPMs to be able to install only
needed stuff, not breaking things, and not introducing too many
dependencies.
Till
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Printing-architecture] PAPI RPM implementation for Mandriva's Cooker
2006-06-14 20:52 [Printing-architecture] PAPI RPM implementation for Mandriva's Cooker Till Kamppeter
@ 2006-06-14 21:03 ` Norm Jacobs
0 siblings, 0 replies; 2+ messages in thread
From: Norm Jacobs @ 2006-06-14 21:03 UTC (permalink / raw)
To: Till Kamppeter; +Cc: Wendy Phillips, printing-architecture
Thanks for the pointer. I will incorporate the RPM spec file
into the subversion repository today (hopefully)
-Norm
Till Kamppeter wrote:
> Oi,
>
> in todays architecture telecon we have talked about the implementration
> of PAPI in the distros and my PAPI RPMs for Mandriva.
>
> Here you find source and binary RPMs for Mandriva's Cooker and also the
> source tarball (SVN rev 171) and the spec file:
>
> http://www.freestandards.org/~till/tmp/papi/
>
> There are no patches, all file manipulation is done with Perl. The
> libraries are renamed and selected by update-alternatives (default is
> IPP library for CUPS), as libpapi-dynamic does not work very well with
> CUPS. This scheme should perhaps be adopted upstream for easier
> integration in distros.
>
Yes, the libpapi-dynamic support uses /etc/printers.conf, which
doesn't exist on linux distros. Replacing libpapi with a link to
psm-ipp will make it talk directly (no interposed library) to an
IPP server (CUPS). psm-ipp also understands the CUPS_SERVER
and a PAPI_SERVICE_URI environment variable to override any
autoconf provided default default ipp service uri.
> You also see the splitting of binary RPMs to be able to install only
> needed stuff, not breaking things, and not introducing too many
> dependencies.
>
> Till
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-06-14 21:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-14 20:52 [Printing-architecture] PAPI RPM implementation for Mandriva's Cooker Till Kamppeter
2006-06-14 21:03 ` Norm Jacobs
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.