<?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: Google SoC 2009: keep thinking	</title>
	<atom:link href="https://www.dragonflydigest.com/2009/02/07/google-soc-2009-keep-thinking/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2009/02/07/google-soc-2009-keep-thinking/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Sun, 08 Feb 2009 05:33:27 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Joe "Floid" Kanowitz		</title>
		<link>https://www.dragonflydigest.com/2009/02/07/google-soc-2009-keep-thinking/comment-page-1/#comment-29326</link>

		<dc:creator><![CDATA[Joe "Floid" Kanowitz]]></dc:creator>
		<pubDate>Sun, 08 Feb 2009 05:33:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=3772#comment-29326</guid>

					<description><![CDATA[Two or ten wishlisty suggestions from me:

* I haven&#039;t had time to check recently, but GNOME support could always be better.  Are we still unsupported in libgtop?  [I was meaning to try to poke that over the holidays but still haven&#039;t had time to even look.]

* Again, I haven&#039;t really looked, but a default configuration or /usr/share/examples contribution for a hostapd (plus pf?) configuration that would *only route to the Internet* would be neat and save hours of individual users&#039; setup time.  Need an AP somewhere?  Have guests over?  Bonus points for running both secured-local and unsecured Internet-only at the same time...

* I keep looking for a &quot;deinstall depends&quot; target in pkgsrc and not finding one; if this is really missing and I&#039;m not braindead, that&#039;d help get out of common SNAFUs.  (Like if you want to be *sure* you&#039;ve removed all of xorg, rather than only the meta-pkg...)

* I&#039;m probably one of two DragonFly-using GNOME fans; I gather KDE gets all the love but I haven&#039;t had a chance to try it on DragonFly.  Given the risk of pkgsrc nightmares if installing it the usual way, is anyone feeling punchy enough to write a script that collects everything into one monolithic &quot;KDE desktop&quot; package?  This could reduce the setup-and-tinkering time for users who just want *a* desktop, and remain optional-but-available for everyone else.]]></description>
			<content:encoded><![CDATA[<p>Two or ten wishlisty suggestions from me:</p>
<p>* I haven&#8217;t had time to check recently, but GNOME support could always be better.  Are we still unsupported in libgtop?  [I was meaning to try to poke that over the holidays but still haven&#8217;t had time to even look.]</p>
<p>* Again, I haven&#8217;t really looked, but a default configuration or /usr/share/examples contribution for a hostapd (plus pf?) configuration that would *only route to the Internet* would be neat and save hours of individual users&#8217; setup time.  Need an AP somewhere?  Have guests over?  Bonus points for running both secured-local and unsecured Internet-only at the same time&#8230;</p>
<p>* I keep looking for a &#8220;deinstall depends&#8221; target in pkgsrc and not finding one; if this is really missing and I&#8217;m not braindead, that&#8217;d help get out of common SNAFUs.  (Like if you want to be *sure* you&#8217;ve removed all of xorg, rather than only the meta-pkg&#8230;)</p>
<p>* I&#8217;m probably one of two DragonFly-using GNOME fans; I gather KDE gets all the love but I haven&#8217;t had a chance to try it on DragonFly.  Given the risk of pkgsrc nightmares if installing it the usual way, is anyone feeling punchy enough to write a script that collects everything into one monolithic &#8220;KDE desktop&#8221; package?  This could reduce the setup-and-tinkering time for users who just want *a* desktop, and remain optional-but-available for everyone else.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
