<?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: GLEP 55 Madness</title>
	<atom:link href="http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/feed/" rel="self" type="application/rss+xml" />
	<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/</link>
	<description>Spewing code in the wrong direction</description>
	<lastBuildDate>Sat, 13 Mar 2010 17:40:01 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ciaran McCreesh</title>
		<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/comment-page-1/#comment-272</link>
		<dc:creator>Ciaran McCreesh</dc:creator>
		<pubDate>Sun, 17 May 2009 01:24:23 +0000</pubDate>
		<guid isPermaLink="false">http://ken.ath.cx/kens_code_pit/?p=214#comment-272</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-271&quot;&gt;
&lt;p&gt;Last time I read GLEP 55 it only indirectly addresses versions through new EAPI’s.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;That&#039;s always been one of the critical points of GLEP 55. It&#039;s right up there in the problem description at the start.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;The only issue I see to that is that older PM’s would not know to search the EAPI inside without sourcing the entire thing and thus erroring out. Any new package managers would be aware of the new change (either filename or my proposal).&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;At best, you&#039;d be forcing the package manager to extract metadata for every version of a package before it can do anything. Currently package managers can just start at the best version and work downwards until they find something suitable.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Assuming this is what you meant, I admit I did not consider older versions of PM’s, mainly as there will almost always be users out there with crap so old its a lost cause.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;It&#039;s not a lost cause, that&#039;s the point. GLEP 55 does what EAPIs were supposed to do -- it removes the need to break older package managers.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-271">
<p>Last time I read GLEP 55 it only indirectly addresses versions through new EAPI’s.</p></blockquote>

<p>That&#8217;s always been one of the critical points of GLEP 55. It&#8217;s right up there in the problem description at the start.</p>

<blockquote><p>The only issue I see to that is that older PM’s would not know to search the EAPI inside without sourcing the entire thing and thus erroring out. Any new package managers would be aware of the new change (either filename or my proposal).</p></blockquote>

<p>At best, you&#8217;d be forcing the package manager to extract metadata for every version of a package before it can do anything. Currently package managers can just start at the best version and work downwards until they find something suitable.</p>

<blockquote><p>Assuming this is what you meant, I admit I did not consider older versions of PM’s, mainly as there will almost always be users out there with crap so old its a lost cause.</p></blockquote>

<p>It&#8217;s not a lost cause, that&#8217;s the point. GLEP 55 does what EAPIs were supposed to do &#8212; it removes the need to break older package managers.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/comment-page-1/#comment-271</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Sun, 17 May 2009 01:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://ken.ath.cx/kens_code_pit/?p=214#comment-271</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-270&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-270&quot; rel=&quot;nofollow&quot;&gt;Ciaran McCreesh&lt;/a&gt; :&lt;/strong&gt;
&lt;P&gt;How do you plan to fix the arbitrary and pointless restrictions forbidding versions like 1.2.3-rc1 without GLEP 55?&lt;/P&gt;         &lt;/blockquote&gt;

&lt;p&gt;Last time I read GLEP 55 it only indirectly addresses versions through new EAPI&#039;s.&lt;/p&gt;

&lt;p&gt;The only issue I see to that is that older PM&#039;s would not know to search the EAPI inside without sourcing the entire thing and thus erroring out. Any new package managers would be aware of the new change (either filename or my proposal).&lt;/p&gt;

&lt;p&gt;Assuming this is what you meant, I admit I did not consider older versions of PM&#039;s, mainly as there will almost always be users out there with crap so old its a lost cause.&lt;/p&gt;

&lt;p&gt;I will agree with you that I find it disturbing this GLEP is still being discussed for over a year. It should be polished if it needs it and shipped off for voting.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-270">
<strong><a href="#comment-270" rel="nofollow">Ciaran McCreesh</a> :</strong>
<p>How do you plan to fix the arbitrary and pointless restrictions forbidding versions like 1.2.3-rc1 without GLEP 55?</p>         </blockquote>

<p>Last time I read GLEP 55 it only indirectly addresses versions through new EAPI&#8217;s.</p>

<p>The only issue I see to that is that older PM&#8217;s would not know to search the EAPI inside without sourcing the entire thing and thus erroring out. Any new package managers would be aware of the new change (either filename or my proposal).</p>

<p>Assuming this is what you meant, I admit I did not consider older versions of PM&#8217;s, mainly as there will almost always be users out there with crap so old its a lost cause.</p>

<p>I will agree with you that I find it disturbing this GLEP is still being discussed for over a year. It should be polished if it needs it and shipped off for voting.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ciaran McCreesh</title>
		<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/comment-page-1/#comment-270</link>
		<dc:creator>Ciaran McCreesh</dc:creator>
		<pubDate>Sat, 16 May 2009 23:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://ken.ath.cx/kens_code_pit/?p=214#comment-270</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-269&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-269&quot; rel=&quot;nofollow&quot;&gt;Ken&lt;/a&gt; :&lt;/strong&gt;

&lt;p&gt;I see no concrete reason why this filename game is better in any kind of way.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;How do you plan to fix the arbitrary and pointless restrictions forbidding versions like 1.2.3-rc1 without GLEP 55?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-269">
<strong><a href="#comment-269" rel="nofollow">Ken</a> :</strong>

<p>I see no concrete reason why this filename game is better in any kind of way.</p>
</blockquote>

<p>How do you plan to fix the arbitrary and pointless restrictions forbidding versions like 1.2.3-rc1 without GLEP 55?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ken</title>
		<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/comment-page-1/#comment-269</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Sat, 16 May 2009 23:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://ken.ath.cx/kens_code_pit/?p=214#comment-269</guid>
		<description>&lt;blockquote cite=&quot;#commentbody-266&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-266&quot; rel=&quot;nofollow&quot;&gt;Ciaran McCreesh&lt;/a&gt; :&lt;/strong&gt;
          &lt;P&gt;The only reason this is still being discussed is that people like you go around commenting on things you don’t understand. Your post is chock full of nonsense and you clearly don’t have a clue what we’re discussing. Kindly shut up until you do — posts like yours are part of the problem, not part of the solution.&lt;/P&gt;         &lt;/blockquote&gt;

&lt;p&gt;Sorry, I&#039;ll voice my opinion on whatever I want. I don&#039;t see a solution in this GLEP, just more beating around the woods and bastardization of portage.&lt;/p&gt;

&lt;p&gt;I see no concrete reason why this filename game is better in any kind of way.&lt;/p&gt;

&lt;blockquote cite=&quot;#commentbody-267&quot;&gt;
&lt;strong&gt;&lt;a href=&quot;#comment-267&quot; rel=&quot;nofollow&quot;&gt;Maciej Piechotka&lt;/a&gt; :&lt;/strong&gt;
          &lt;P&gt;In GLEP 55 there are specified counter-arguments against such solution.&lt;/blockquote&gt;

&lt;p&gt;Sorry I see no counter-arguments, care to actually list one than just proposing its invalid without cause?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote cite="#commentbody-266">
<strong><a href="#comment-266" rel="nofollow">Ciaran McCreesh</a> :</strong>
          <p>The only reason this is still being discussed is that people like you go around commenting on things you don’t understand. Your post is chock full of nonsense and you clearly don’t have a clue what we’re discussing. Kindly shut up until you do — posts like yours are part of the problem, not part of the solution.</p>         </blockquote>

<p>Sorry, I&#8217;ll voice my opinion on whatever I want. I don&#8217;t see a solution in this GLEP, just more beating around the woods and bastardization of portage.</p>

<p>I see no concrete reason why this filename game is better in any kind of way.</p>

<blockquote cite="#commentbody-267">
<strong><a href="#comment-267" rel="nofollow">Maciej Piechotka</a> :</strong>
          <p>In GLEP 55 there are specified counter-arguments against such solution.</p></blockquote>

<p>Sorry I see no counter-arguments, care to actually list one than just proposing its invalid without cause?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: rik</title>
		<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/comment-page-1/#comment-268</link>
		<dc:creator>rik</dc:creator>
		<pubDate>Sat, 16 May 2009 22:55:53 +0000</pubDate>
		<guid isPermaLink="false">http://ken.ath.cx/kens_code_pit/?p=214#comment-268</guid>
		<description>&lt;p&gt;&quot;The proposed solution is to use EAPI-suffixed file extensions for ebuilds. &quot;&lt;/p&gt;

&lt;p&gt;As in exheres-0 ?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&#8220;The proposed solution is to use EAPI-suffixed file extensions for ebuilds. &#8220;</p>

<p>As in exheres-0 ?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Maciej Piechotka</title>
		<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/comment-page-1/#comment-267</link>
		<dc:creator>Maciej Piechotka</dc:creator>
		<pubDate>Sat, 16 May 2009 22:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://ken.ath.cx/kens_code_pit/?p=214#comment-267</guid>
		<description>&lt;p&gt;In GLEP 55 there are specified counter-arguments against such solution. About the &#039;Umm, every new EAPI pretty much breaks backwards compatibility.&#039; it is not a counter argument - EAPI does not directly break backwards compatibility in package manager. I.e. package manager supporting EAPI 2 does not fails with EAPI 1 package. However with such restriction it will fail despite the ebuild was valid (it does not matter if it is well-written or not - as long as it follows the standard it should be accepted).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>In GLEP 55 there are specified counter-arguments against such solution. About the &#8216;Umm, every new EAPI pretty much breaks backwards compatibility.&#8217; it is not a counter argument &#8211; EAPI does not directly break backwards compatibility in package manager. I.e. package manager supporting EAPI 2 does not fails with EAPI 1 package. However with such restriction it will fail despite the ebuild was valid (it does not matter if it is well-written or not &#8211; as long as it follows the standard it should be accepted).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ciaran McCreesh</title>
		<link>http://ken.ath.cx/kens_code_pit/2009/05/16/glep-55-madness/comment-page-1/#comment-266</link>
		<dc:creator>Ciaran McCreesh</dc:creator>
		<pubDate>Sat, 16 May 2009 21:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://ken.ath.cx/kens_code_pit/?p=214#comment-266</guid>
		<description>&lt;p&gt;The only reason this is still being discussed is that people like you go around commenting on things you don&#039;t understand. Your post is chock full of nonsense and you clearly don&#039;t have a clue what we&#039;re discussing. Kindly shut up until you do -- posts like yours are part of the problem, not part of the solution.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The only reason this is still being discussed is that people like you go around commenting on things you don&#8217;t understand. Your post is chock full of nonsense and you clearly don&#8217;t have a clue what we&#8217;re discussing. Kindly shut up until you do &#8212; posts like yours are part of the problem, not part of the solution.</p>]]></content:encoded>
	</item>
</channel>
</rss>
