<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.5" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Josh Saddler - Latest comments on Hands on with ebuilds: Abiword 2.7</title>
		<link>http://blogs.gentoo.org/nightmorph?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.5"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: Hands on with ebuilds: Abiword 2.7</title>
			<pubDate>Sun, 12 Jul 2009 07:32:37 +0000</pubDate>
			<dc:creator>foser [Visitor]</dc:creator>
			<guid isPermaLink="false">c21635@http://blogs.gentoo.org/</guid>
			<description>Regarding removing minimum versions in dependencies, if they're still noted in the configure scripts it is best to leave them intact and make the ebuild dependencies confirm with the config dependencies. Not all people choose to update all of their system all the time and this may leave old libraries around. e.g. I have this server system where i only do glsa updates, this has been working fine for years (for real) . Now say hypothetical I want to upgrade my abiword and I still have =wv-1.0*  around on this system, the ebuild would now fail on an abiword merge because this version is too old and abi incompatible.&lt;br /&gt;
&lt;br /&gt;
In short, if you want to practice correct ebuilding you adhere to the package config script dependencies and do not 'fix' the ebuilds deps based on the _current_ state of the tree.</description>
			<content:encoded><![CDATA[Regarding removing minimum versions in dependencies, if they're still noted in the configure scripts it is best to leave them intact and make the ebuild dependencies confirm with the config dependencies. Not all people choose to update all of their system all the time and this may leave old libraries around. e.g. I have this server system where i only do glsa updates, this has been working fine for years (for real) . Now say hypothetical I want to upgrade my abiword and I still have =wv-1.0*  around on this system, the ebuild would now fail on an abiword merge because this version is too old and abi incompatible.<br />
<br />
In short, if you want to practice correct ebuilding you adhere to the package config script dependencies and do not 'fix' the ebuilds deps based on the _current_ state of the tree.]]></content:encoded>
			<link>http://blogs.gentoo.org/nightmorph/2009/05/14/hands-on-with-ebuilds-abiword#c21635</link>
		</item>
			</channel>
</rss>
