<?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: KDE 3.4 arrives, Gnome 2.10 hits FreeBSD ports	</title>
	<atom:link href="https://www.dragonflydigest.com/2005/03/16/kde-34-arrives-gnome-210-hits-freebsd-ports/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2005/03/16/kde-34-arrives-gnome-210-hits-freebsd-ports/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Sat, 19 Mar 2005 00:33:58 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.4</generator>
	<item>
		<title>
		By: Guillermo GarcÃ­a Rojas		</title>
		<link>https://www.dragonflydigest.com/2005/03/16/kde-34-arrives-gnome-210-hits-freebsd-ports/comment-page-1/#comment-459</link>

		<dc:creator><![CDATA[Guillermo GarcÃ­a Rojas]]></dc:creator>
		<pubDate>Sat, 19 Mar 2005 00:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=1016#comment-459</guid>

					<description><![CDATA[The script does not work under DFly, even if you change it to deal with 1.1 version. It removes your existing GNOME installation and it&#039;s done.

I have to go to FreeBSD 4.9-RELEASE, make all the GNOME port and go back to DFly, because of a mess I did on my box.

But I find that some GNOME ports build ok on DFly.


]]></description>
			<content:encoded><![CDATA[<p>The script does not work under DFly, even if you change it to deal with 1.1 version. It removes your existing GNOME installation and it&#8217;s done.</p>
<p>I have to go to FreeBSD 4.9-RELEASE, make all the GNOME port and go back to DFly, because of a mess I did on my box.</p>
<p>But I find that some GNOME ports build ok on DFly.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
