All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norm Jacobs <Norm.Jacobs@Sun.COM>
To: Till Kamppeter <till.kamppeter@gmx.net>
Cc: Wendy Phillips <wendyp@Sun.COM>,
	printing-architecture <printing-architecture@freestandards.org>
Subject: Re: [Printing-architecture] PAPI RPM implementation for Mandriva's Cooker
Date: Wed, 14 Jun 2006 16:03:03 -0500	[thread overview]
Message-ID: <44907987.5040604@Sun.COM> (raw)
In-Reply-To: <44907703.50807@gmx.net>

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
>   


      reply	other threads:[~2006-06-14 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 20:52 [Printing-architecture] PAPI RPM implementation for Mandriva's Cooker Till Kamppeter
2006-06-14 21:03 ` Norm Jacobs [this message]

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=44907987.5040604@Sun.COM \
    --to=norm.jacobs@sun.com \
    --cc=printing-architecture@freestandards.org \
    --cc=till.kamppeter@gmx.net \
    --cc=wendyp@Sun.COM \
    /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.