<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Webshop and GLIBC</title>
	<atom:link href="http://thomas.apestaart.org/log/?p=457&#038;feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://thomas.apestaart.org/log/?p=457</link>
	<description>Present Perfect</description>
	<lastBuildDate>Tue, 21 May 2013 03:19:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: michael schurter &#187; Blog Archive &#187; Debian Etch Released</title>
		<link>http://thomas.apestaart.org/log/?p=457&#038;cpage=1#comment-1985</link>
		<dc:creator>michael schurter &#187; Blog Archive &#187; Debian Etch Released</dc:creator>
		<pubDate>Sun, 08 Apr 2007 18:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://thomas.apestaart.org/log/?p=457#comment-1985</guid>
		<description>[...] ancient version of the standard C library (2.3.6) means poor compatibility with 3rd party binaries (which Debian has always hated [...]</description>
		<content:encoded><![CDATA[<p>[...] ancient version of the standard C library (2.3.6) means poor compatibility with 3rd party binaries (which Debian has always hated [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Me</title>
		<link>http://thomas.apestaart.org/log/?p=457&#038;cpage=1#comment-1368</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Mon, 02 Apr 2007 17:19:05 +0000</pubDate>
		<guid isPermaLink="false">http://thomas.apestaart.org/log/?p=457#comment-1368</guid>
		<description>Autopackage guys know a lot about these kind of problems. They have a good infrainstructure that allows you to compile in a distribution with glibc 2.4 without having any dependency with glibc 2.4 symbols in an easy way.
http://autopackage.org/community.html</description>
		<content:encoded><![CDATA[<p>Autopackage guys know a lot about these kind of problems. They have a good infrainstructure that allows you to compile in a distribution with glibc 2.4 without having any dependency with glibc 2.4 symbols in an easy way.<br />
<a href="http://autopackage.org/community.html" rel="nofollow">http://autopackage.org/community.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://thomas.apestaart.org/log/?p=457&#038;cpage=1#comment-1180</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Wed, 28 Mar 2007 19:41:18 +0000</pubDate>
		<guid isPermaLink="false">http://thomas.apestaart.org/log/?p=457#comment-1180</guid>
		<description>Hi Phil,

the problem is not necessary the knowledge on how to do it, it&#039;s purely time.  I&#039;m sure we&#039;ll get to it in the future, but right now we&#039;re all busy on something and we&#039;d prefer to fix actual bugs in those plugins than to spend some time doing the right solution for the distribution at the moment.</description>
		<content:encoded><![CDATA[<p>Hi Phil,</p>
<p>the problem is not necessary the knowledge on how to do it, it&#8217;s purely time.  I&#8217;m sure we&#8217;ll get to it in the future, but right now we&#8217;re all busy on something and we&#8217;d prefer to fix actual bugs in those plugins than to spend some time doing the right solution for the distribution at the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Armstrong</title>
		<link>http://thomas.apestaart.org/log/?p=457&#038;cpage=1#comment-1175</link>
		<dc:creator>Phil Armstrong</dc:creator>
		<pubDate>Wed, 28 Mar 2007 10:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://thomas.apestaart.org/log/?p=457#comment-1175</guid>
		<description>Obviously shipping two sets of plugins would be silly. But you could just build the all the plugins against glibc 2.3 in the first place.

Creating a Debian build environment on the fly is *very* easy. Prod me if you want a guide.

Phil</description>
		<content:encoded><![CDATA[<p>Obviously shipping two sets of plugins would be silly. But you could just build the all the plugins against glibc 2.3 in the first place.</p>
<p>Creating a Debian build environment on the fly is *very* easy. Prod me if you want a guide.</p>
<p>Phil</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Licquia Blog &#187; Blog Archive &#187; Getting the Message Out</title>
		<link>http://thomas.apestaart.org/log/?p=457&#038;cpage=1#comment-1174</link>
		<dc:creator>The Licquia Blog &#187; Blog Archive &#187; Getting the Message Out</dc:creator>
		<pubDate>Tue, 27 Mar 2007 20:52:19 +0000</pubDate>
		<guid isPermaLink="false">http://thomas.apestaart.org/log/?p=457#comment-1174</guid>
		<description>[...] From a Fluendo employee: Are we evil that we don’t take more hours out of our day to build on glibc 2.3 ? You bet, we are cold heartless bastards. But in reality 90% of the people on glibc 2.3 are users that have an upgrade path to a more recent version of their distro; the other people are future Debian Etch users. I’m sure the Etch releasers have convinced themselves of the usefulness of not releasing with a glibc 2.4 that is more than 15 months old, and instead opt for an even older series, even before they actually release. But I am starting to wonder more and more who the people are that are waiting for a release like this. Realistically speaking, it is possible that we may add glibc 2.3 plugins in the future if we see that more than just Debian is affected. We are not against taking your money for giving you a service that works. But the hours in our day are just as scarce as they are in yours. I just wanted to explain this to people that want to know, to take away your incentive to complain about a nameless faceless Company being Evil to you. [...]</description>
		<content:encoded><![CDATA[<p>[...] From a Fluendo employee: Are we evil that we don’t take more hours out of our day to build on glibc 2.3 ? You bet, we are cold heartless bastards. But in reality 90% of the people on glibc 2.3 are users that have an upgrade path to a more recent version of their distro; the other people are future Debian Etch users. I’m sure the Etch releasers have convinced themselves of the usefulness of not releasing with a glibc 2.4 that is more than 15 months old, and instead opt for an even older series, even before they actually release. But I am starting to wonder more and more who the people are that are waiting for a release like this. Realistically speaking, it is possible that we may add glibc 2.3 plugins in the future if we see that more than just Debian is affected. We are not against taking your money for giving you a service that works. But the hours in our day are just as scarce as they are in yours. I just wanted to explain this to people that want to know, to take away your incentive to complain about a nameless faceless Company being Evil to you. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
