<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>costela.net &#187; pbuilder</title>
	<atom:link href="http://costela.net/tag/pbuilder/feed/" rel="self" type="application/rss+xml" />
	<link>http://costela.net</link>
	<description>rhetorically impaired, ironically despaired</description>
	<lastBuildDate>Wed, 25 Jan 2012 15:30:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
		<item>
		<title>Re: Making pbuilder just that little bit faster</title>
		<link>http://costela.net/2009/12/re-making-pbuilder-just-that-little-bit-faster/</link>
		<comments>http://costela.net/2009/12/re-making-pbuilder-just-that-little-bit-faster/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 22:45:33 +0000</pubDate>
		<dc:creator>Leo Antunes</dc:creator>
				<category><![CDATA[Home]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[debian planet]]></category>
		<category><![CDATA[pbuilder]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://costela.net/?p=528</guid>
		<description><![CDATA[Absolutely, but there are at least two workarounds: Adding BINDMOUNTS=&#34;/var/cache/apt/archives&#34; APTCACHE=&#34;&#34; to your .pbuilderrc, in case you don&#8217;t need any special separation of local and pbuilder caches (that&#8217;s my case). Using apt-proxy or the like, which has its overhead, but also its other advantages. None of them seem all that bad to me, considering the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.wgdd.de/?p=74">Absolutely</a>, but there are at least two workarounds:</p>
<ol>
<li>Adding

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;"><span style="color: #007800;">BINDMOUNTS</span>=<span style="color: #ff0000;">&quot;/var/cache/apt/archives&quot;</span>
<span style="color: #007800;">APTCACHE</span>=<span style="color: #ff0000;">&quot;&quot;</span></pre></div></div>

<p> to your .pbuilderrc, in case you don&#8217;t need any special separation of local and pbuilder caches (that&#8217;s my case).</li>
<li>Using apt-proxy or the like, which has its overhead, but also its other advantages.</li>
</ol>
<p>None of them seem all that bad to me, considering the sensible speed improvements to pbuilder, but the ultimate decision probably depends on the amount of disk-access the packages in question need.</p>
]]></content:encoded>
			<wfw:commentRss>http://costela.net/2009/12/re-making-pbuilder-just-that-little-bit-faster/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

