Date: Sat, 06 Jul 2002 02:19:31 +0200
   From: Till Kamppeter <[EMAIL PROTECTED]>

   The GIMP plug-in could well be part of the GIMP, but then users
   without printers need to install libgimpprint. Perhaps it is best
   when the plug-in would be a stand-alone package. Or when there is
   no libgimpprint and one compiles the GIMP, the plug-in will not be
   compiled.

That is, of course, if somebody doesn't rewrite the plug-in to not use
libgimpprint at all.  However, I think the best thing to do is for the
GIMP's configure script to autodetect libgimpprint and build it if
available (just like it does for, e. g. JPEG import/export).

   So all in all I agree with your splitting suggested above. By the
   way, I will probably also split Foomatic: into the XML database,
   the databse engine (the stuff which generates PPDs and sets up
   queues), and the filter scripts. This will solve many updating
   problems.

Can you also think about how to handle generation of the XML database?
We've never promised stability in terms of printers and supported
printer functionality, and I think it's necessary for this stuff to be
generatable on the fly.

-- 
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
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Reply via email to