<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Unhooking the foomatic parser</title>
	<atom:link href="http://cyberelk.net/tim/2007/06/08/unhooking-the-foomatic-parser/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyberelk.net/tim/2007/06/08/unhooking-the-foomatic-parser/</link>
	<description></description>
	<pubDate>Tue, 07 Oct 2008 02:34:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: tim</title>
		<link>http://cyberelk.net/tim/2007/06/08/unhooking-the-foomatic-parser/#comment-267</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Fri, 08 Jun 2007 22:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2007/06/08/unhooking-the-foomatic-parser/#comment-267</guid>
		<description>Not really.  Yes, we can remove the dependency on foomatic in the system-config-printer package, but we would still want the foomatic package installed by default for the wide range of devices it can supply PPDs for.  In other words, you can avoid installing foomatic, but you won't get nearly so many PPDs in that case.

Foomatic provides a CUPS driver script, &lt;tt&gt;/usr/lib/cups/driver/foomatic&lt;/tt&gt;, which CUPS uses to fetch a list of PPDs when it needs it (on demand).  So listing the available PPDs with "lpinfo -m" shows the PPDs that foomatic is capable of generating in addition to the PPDs that CUPS already has.

We had been parsing the foomatic database in addition to this (meaning that it got parsed twice, actually), but unhooking our own parser means that we can make system-config-printer a "pure" CUPS configuration program, and that brings with it some benefits.  Most notably, the "recommended driver" can now potentially include CUPS drivers, or PPDs from manufacturers, whereas before it was always the foomatic driver.

It also means that hal-cups-utils will be able to choose the best available PPD for a given device, without being restricted to foomatic PPDs (as it is in F-7).</description>
		<content:encoded><![CDATA[<p>Not really.  Yes, we can remove the dependency on foomatic in the system-config-printer package, but we would still want the foomatic package installed by default for the wide range of devices it can supply PPDs for.  In other words, you can avoid installing foomatic, but you won&#8217;t get nearly so many PPDs in that case.</p>
<p>Foomatic provides a CUPS driver script, <tt>/usr/lib/cups/driver/foomatic</tt>, which CUPS uses to fetch a list of PPDs when it needs it (on demand).  So listing the available PPDs with &#8220;lpinfo -m&#8221; shows the PPDs that foomatic is capable of generating in addition to the PPDs that CUPS already has.</p>
<p>We had been parsing the foomatic database in addition to this (meaning that it got parsed twice, actually), but unhooking our own parser means that we can make system-config-printer a &#8220;pure&#8221; CUPS configuration program, and that brings with it some benefits.  Most notably, the &#8220;recommended driver&#8221; can now potentially include CUPS drivers, or PPDs from manufacturers, whereas before it was always the foomatic driver.</p>
<p>It also means that hal-cups-utils will be able to choose the best available PPD for a given device, without being restricted to foomatic PPDs (as it is in F-7).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Katz</title>
		<link>http://cyberelk.net/tim/2007/06/08/unhooking-the-foomatic-parser/#comment-266</link>
		<dc:creator>Jeremy Katz</dc:creator>
		<pubDate>Fri, 08 Jun 2007 18:18:09 +0000</pubDate>
		<guid isPermaLink="false">http://cyberelk.net/tim/2007/06/08/unhooking-the-foomatic-parser/#comment-266</guid>
		<description>Does this mean that the foomatic package will be able to stop being installed by default?</description>
		<content:encoded><![CDATA[<p>Does this mean that the foomatic package will be able to stop being installed by default?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
