<?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"
	>
<channel>
	<title>Comments on: Wget on Mac?</title>
	<atom:link href="http://blog.codevader.com/2009/06/11/wget-on-mac/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.codevader.com/2009/06/11/wget-on-mac/</link>
	<description>Thoughts from the nice people at Codevader :)</description>
	<pubDate>Thu, 11 Mar 2010 09:37:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Andy Volk</title>
		<link>http://blog.codevader.com/2009/06/11/wget-on-mac/#comment-895</link>
		<dc:creator>Andy Volk</dc:creator>
		<pubDate>Tue, 20 Oct 2009 20:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.codevader.com/?p=103#comment-895</guid>
		<description>Agreed -- wget definitely should be part of the default kit, at least for users who have Xcode installed.

To add another perspective, my preferred way to install wget is to install it through macports, since it makes version management (and rebuilding all those custom-installed applications from source after the 64-bit Snow Leopard upgrade!) much easier: http://www.macports.org/</description>
		<content:encoded><![CDATA[<p>Agreed &#8212; wget definitely should be part of the default kit, at least for users who have Xcode installed.</p>
<p>To add another perspective, my preferred way to install wget is to install it through macports, since it makes version management (and rebuilding all those custom-installed applications from source after the 64-bit Snow Leopard upgrade!) much easier: <a href="http://www.macports.org/" rel="nofollow">http://www.macports.org/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
