<?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: Debian- What It Means To Me</title>
	<atom:link href="http://pthree.org/2008/12/21/debian-what-it-means-to-me/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Wed, 08 Feb 2012 02:59:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha</generator>
	<item>
		<title>By: Patrick</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109183</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sat, 27 Dec 2008 16:08:25 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109183</guid>
		<description>So now you either want to prove your ignorance to the real job of package maintainers or you just want to flame (ok flaming is actually all this post and most of the comments is about, but well, you can think of what I mean).

So what about bug triaging, analysing crash reports, analyse and setup steps to get upgrades and transitions done? Adapting software to distribution-specific needs? (e.g. setting up alternatives) Testing? Reporting Bugs upstream? Suggesting fixes to upstream? Are this things that you think can be done by a robot?</description>
		<content:encoded><![CDATA[<p>So now you either want to prove your ignorance to the real job of package maintainers or you just want to flame (ok flaming is actually all this post and most of the comments is about, but well, you can think of what I mean).</p>
<p>So what about bug triaging, analysing crash reports, analyse and setup steps to get upgrades and transitions done? Adapting software to distribution-specific needs? (e.g. setting up alternatives) Testing? Reporting Bugs upstream? Suggesting fixes to upstream? Are this things that you think can be done by a robot?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109182</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sat, 27 Dec 2008 16:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109182</guid>
		<description>&quot;RPM does have pre scripts, and they work rather well. What you’re describing about the upgrade scripts is exactly how it should behave.&quot;

Really? How - for example - do you handle something like diversions with this approach?

&quot;RPM unpacks what’s needed, runs the rest of the pre scripts, then installs, then runs any post scripts that may be present.&quot;

The &quot;whats needed&quot; part is confusing. Does that mean you can mark certain files as not to be installed before certain parts of the preinst script(s) ran? If so, this would be interesting, but a rather strange workaround to the problem that is to be solved.</description>
		<content:encoded><![CDATA[<p>&#8220;RPM does have pre scripts, and they work rather well. What you’re describing about the upgrade scripts is exactly how it should behave.&#8221;</p>
<p>Really? How &#8211; for example &#8211; do you handle something like diversions with this approach?</p>
<p>&#8220;RPM unpacks what’s needed, runs the rest of the pre scripts, then installs, then runs any post scripts that may be present.&#8221;</p>
<p>The &#8220;whats needed&#8221; part is confusing. Does that mean you can mark certain files as not to be installed before certain parts of the preinst script(s) ran? If so, this would be interesting, but a rather strange workaround to the problem that is to be solved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109181</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sat, 27 Dec 2008 15:52:45 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109181</guid>
		<description>Uh? I can say a lot of bad things about aptitude (e.g. that it is horrible slow) but argueing that the dependency resolver is &#039;utterly broken&#039; appears to be just untrue.
In my personal experience (when administrating some couples of Debian systems) my feeling is that the dependency resolver of aptitude works in a more consistent and reliable way then apt-get ever did. I always smile about the moments where it makes a suggestion (not always the one I want, yeah), where apt-get would have failed and asked me to enter a solution on my own.
But I must indeed confess that I did not really use apt-get for at least 6 months, so I cannot really made statements about the eventual progress apt-get made.

Regardless of that I don&#039;t see how this is a bad example. It is relative new, incorporates a clear enhancement to the previous approaches to fix the system (the fact that I don&#039;t need to it manually) and it is an example that in this area something new *has* emerged (contrary to what Aaron said)</description>
		<content:encoded><![CDATA[<p>Uh? I can say a lot of bad things about aptitude (e.g. that it is horrible slow) but argueing that the dependency resolver is &#8216;utterly broken&#8217; appears to be just untrue.<br />
In my personal experience (when administrating some couples of Debian systems) my feeling is that the dependency resolver of aptitude works in a more consistent and reliable way then apt-get ever did. I always smile about the moments where it makes a suggestion (not always the one I want, yeah), where apt-get would have failed and asked me to enter a solution on my own.<br />
But I must indeed confess that I did not really use apt-get for at least 6 months, so I cannot really made statements about the eventual progress apt-get made.</p>
<p>Regardless of that I don&#8217;t see how this is a bad example. It is relative new, incorporates a clear enhancement to the previous approaches to fix the system (the fact that I don&#8217;t need to it manually) and it is an example that in this area something new *has* emerged (contrary to what Aaron said)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109180</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sat, 27 Dec 2008 15:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109180</guid>
		<description>&quot;Aptitude is merely a front end to apt-get.&quot;

You don&#039;t actually believe what you say, do you?

&quot;It’s nothing really innovative.&quot;

Oho. But Launchpad is? You know that you run out of good examples, if you argue against what makes your own examples innovative?</description>
		<content:encoded><![CDATA[<p>&#8220;Aptitude is merely a front end to apt-get.&#8221;</p>
<p>You don&#8217;t actually believe what you say, do you?</p>
<p>&#8220;It’s nothing really innovative.&#8221;</p>
<p>Oho. But Launchpad is? You know that you run out of good examples, if you argue against what makes your own examples innovative?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109169</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:42:33 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109169</guid>
		<description>Yeah, I&#039;ve read that. It&#039;s been ridiculed fairly hard on a number of topics:

1. He&#039;s pulling from Git logs, which is only a recent tracker of the kernel development.
2. He&#039;s only using vanity email addresses, which until recently, Canonical and Ubuntu didn&#039;t hand out.
3. Classic example of the pot calling the kettle black.
4. Ubuntu has giving back to the Linux community 100 times more than any kernel developer has done. If it weren&#039;t for Ubuntu, Linux on the desktop would not be where it is today.</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;ve read that. It&#8217;s been ridiculed fairly hard on a number of topics:</p>
<p>1. He&#8217;s pulling from Git logs, which is only a recent tracker of the kernel development.<br />
2. He&#8217;s only using vanity email addresses, which until recently, Canonical and Ubuntu didn&#8217;t hand out.<br />
3. Classic example of the pot calling the kettle black.<br />
4. Ubuntu has giving back to the Linux community 100 times more than any kernel developer has done. If it weren&#8217;t for Ubuntu, Linux on the desktop would not be where it is today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109168</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109168</guid>
		<description>Bazaar fills needs that other VCS software doesn&#039;t give. Isn&#039;t this the whole point of Free Software? If it doesn&#039;t have Feature X, then either patch it, fork it, or create anew.

Also, graphics and overall look and feel can be called innovation. Novell artwork in the SUSE distributions is beautiful, and frankly, no distro even comes close.

And yes, Canonical was &quot;slammed&quot; for not doing kernel development by a Novell employee who also had done little kernel development. Isn&#039;t this the pot calling the kettle black? Further, where are the &quot;Debian Developer&quot; contributions to the kernel? Oh, not as much as expected, eh?</description>
		<content:encoded><![CDATA[<p>Bazaar fills needs that other VCS software doesn&#8217;t give. Isn&#8217;t this the whole point of Free Software? If it doesn&#8217;t have Feature X, then either patch it, fork it, or create anew.</p>
<p>Also, graphics and overall look and feel can be called innovation. Novell artwork in the SUSE distributions is beautiful, and frankly, no distro even comes close.</p>
<p>And yes, Canonical was &#8220;slammed&#8221; for not doing kernel development by a Novell employee who also had done little kernel development. Isn&#8217;t this the pot calling the kettle black? Further, where are the &#8220;Debian Developer&#8221; contributions to the kernel? Oh, not as much as expected, eh?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109167</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109167</guid>
		<description>LinuxCanuck is free to express his opinions and feelings towards Debian. I don&#039;t see anything in the post that would compromise the Code of Conduct. He did get a few facts wrong, which were mentioned to him in the comments, but his post is expressing his feelings, and I hope he can do that on his own blog.</description>
		<content:encoded><![CDATA[<p>LinuxCanuck is free to express his opinions and feelings towards Debian. I don&#8217;t see anything in the post that would compromise the Code of Conduct. He did get a few facts wrong, which were mentioned to him in the comments, but his post is expressing his feelings, and I hope he can do that on his own blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109166</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109166</guid>
		<description>The storm ORM is quite a bit different than MySQL. The ORM is sheer code to power MySQL or other databases, where MySQL is the database itself, so your analogy fails.</description>
		<content:encoded><![CDATA[<p>The storm ORM is quite a bit different than MySQL. The ORM is sheer code to power MySQL or other databases, where MySQL is the database itself, so your analogy fails.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109165</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:17:19 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109165</guid>
		<description>I agree that Ubuntu should be taking greater advantage of Upstart. Right now, it&#039;s in SysVInit backwards compatibility mode, and it seems the Ubuntu developers are sitting on their hands, waiting for something magical to happen before taking full advantage of it. The same can be said with Fedora.</description>
		<content:encoded><![CDATA[<p>I agree that Ubuntu should be taking greater advantage of Upstart. Right now, it&#8217;s in SysVInit backwards compatibility mode, and it seems the Ubuntu developers are sitting on their hands, waiting for something magical to happen before taking full advantage of it. The same can be said with Fedora.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109164</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109164</guid>
		<description>No, this is the biggest misunderstanding with the whole Firefox-IceWeasel fiasco. The Firefox artwork is free, it&#039;s just trademarked. Debian also has a trademarked logo. Does this make Debian non-free? Trademarks protect the organization and their product. Mozilla is more than happy for you to use the trademark, as long as you follow trademark law, and call it &quot;Mozilla Firefox&quot;.</description>
		<content:encoded><![CDATA[<p>No, this is the biggest misunderstanding with the whole Firefox-IceWeasel fiasco. The Firefox artwork is free, it&#8217;s just trademarked. Debian also has a trademarked logo. Does this make Debian non-free? Trademarks protect the organization and their product. Mozilla is more than happy for you to use the trademark, as long as you follow trademark law, and call it &#8220;Mozilla Firefox&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109163</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:13:25 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109163</guid>
		<description>No, I fully understand what is at task for a package maintainer. Debian has a man page policy for every .deb packaged. Also, they are scrutinized to the rules of the DFSG. Any artwork, documentation, code, or anything else that doesn&#039;t fully comply with the DFSG is rejected or removed. Robots can&#039;t do this, people can.</description>
		<content:encoded><![CDATA[<p>No, I fully understand what is at task for a package maintainer. Debian has a man page policy for every .deb packaged. Also, they are scrutinized to the rules of the DFSG. Any artwork, documentation, code, or anything else that doesn&#8217;t fully comply with the DFSG is rejected or removed. Robots can&#8217;t do this, people can.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109162</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109162</guid>
		<description>I don&#039;t get this &quot;bunch of files on your disk&quot; stuff. Are you suggesting that RPM just downloads whatever it wants, and litters your disk with useless crap? Because if you are, that shows your ignorance towards RPM.

RPM does have pre scripts, and they work rather well. What you&#039;re describing about the upgrade scripts is exactly how it should behave. I believe your confusing &quot;unpacked&quot; with &quot;installed&quot;. RPM unpacks what&#039;s needed, runs the rest of the pre scripts, then installs, then runs any post scripts that may be present.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t get this &#8220;bunch of files on your disk&#8221; stuff. Are you suggesting that RPM just downloads whatever it wants, and litters your disk with useless crap? Because if you are, that shows your ignorance towards RPM.</p>
<p>RPM does have pre scripts, and they work rather well. What you&#8217;re describing about the upgrade scripts is exactly how it should behave. I believe your confusing &#8220;unpacked&#8221; with &#8220;installed&#8221;. RPM unpacks what&#8217;s needed, runs the rest of the pre scripts, then installs, then runs any post scripts that may be present.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109161</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:08:52 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109161</guid>
		<description>This boils down to philosophy, and I think we should agree to disagree on this. You feel if you install a service, it should be setup for you listening for connections. I don&#039;t. We&#039;ll leave it at that.</description>
		<content:encoded><![CDATA[<p>This boils down to philosophy, and I think we should agree to disagree on this. You feel if you install a service, it should be setup for you listening for connections. I don&#8217;t. We&#8217;ll leave it at that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109160</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:07:45 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109160</guid>
		<description>I still count AppArmor and innovation, even if I find SELinux vastly superior. I didn&#039;t just add it to the post, if I didn&#039;t feel that Novell produced it. I don&#039;t just throw random things in the post for nothing.</description>
		<content:encoded><![CDATA[<p>I still count AppArmor and innovation, even if I find SELinux vastly superior. I didn&#8217;t just add it to the post, if I didn&#8217;t feel that Novell produced it. I don&#8217;t just throw random things in the post for nothing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/12/21/debian-what-it-means-to-me/#comment-109159</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Fri, 26 Dec 2008 10:06:24 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=777#comment-109159</guid>
		<description>How is the dependency resolver in aptitude broken? Before aptitude, APT had no way of knowing about orphaned dependencies. Now there&#039;s &#039;apt-get autoremove&#039;, which was inspired by the way aptitude handled these orphaned dependencies. Aptitude is a superior APT.</description>
		<content:encoded><![CDATA[<p>How is the dependency resolver in aptitude broken? Before aptitude, APT had no way of knowing about orphaned dependencies. Now there&#8217;s &#8216;apt-get autoremove&#8217;, which was inspired by the way aptitude handled these orphaned dependencies. Aptitude is a superior APT.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

