From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <47E59FA6.5060405@gmail.com> Date: Sun, 23 Mar 2008 01:09:10 +0100 From: Till Kamppeter MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Printing-architecture] Summer of Code PAPI project List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cherif YAYA Cc: printing-architecture@lists.linux-foundation.org Cherif YAYA wrote: > Also in the TODO file, under the libpapi-cups entry it is said that > "Once libpapi-ipp is complete this can be dropped, because CUPS will > accept jobs from "any" IPP client and the PAPI IPP support is guaranteed > to work." Does that mean that any work done for this project would be > practically useless? It's probably not the case and I'm probably missing > something. But I'd like some clarification as to how the deliverables of > this CUPS integration will contribute to the PAPI effort. For me this looks more like that libpapi-cups' functionality gets merged into libpapi-ipp. Norm, Wendy, am I correct? Till