Just thought I'd send a quick update on what we're up to with
gimp-print.  In 4.1, we've done a major reorganization of our code
base, creating a new shared library (libgimpprint.so) that
applications (such as the print plugin, Ghostscript, and CUPS drivers)
can link against.  The intent is that libgimpprint (which is not
dependent on anything else, such as the Gimp, GTK, etc.) be installed
as part of the underlying infrastructure that the print plugin can
depend upon.  This raises questions of how to package it with the
Gimp.  The Gimp could certainly distribute the whole package with it,
but it's quite large.  It could also be treated like JPEG and only
built if the underlying libgimpprint exists on the system.

Robert Krawitz <[EMAIL PROTECTED]>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail [EMAIL PROTECTED]
Project lead for Gimp Print/stp --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton
Gimp-developer mailing list

Reply via email to