<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel>
<title>swaret</title>
<pubDate>Tue, 30 Jan 2007 08:50:36 -0800</pubDate>
<link>http://swaret.sourceforge.net/</link>
<description>PostNuke Powered Site</description>
<language>en-us</language>
<image>
 <title>swaret</title>
 <url>http://swaret.sourceforge.net/images/favicon.ico</url>
 <link>http://swaret.sourceforge.net/</link>
</image>
<webMaster>linuxsneake&#114;&#064;&#117;sers.sf.net</webMaster>
<item>
<title>Need a Developer</title>
<link>http://swaret.sourceforge.net/Article7.html</link>
<description>For various reasons, I am no longer going to be using Slackware.  I am migrating to a combination of CentOS and Fedora (to mirror the RHEL environment with which I use at work and do development).

However, I do not want to see swaret die.  It fills a much needed void, and has a great future.  If someone could step forward that has PERL experience, uses Slackware, and has time to do some coding on the side, please let me know.  After a grace period, the project can be yours.
Update:  It looks like Dozzie is going to try his hand at this.  We look forward to the next 2.0.0 branch release</description>
<pubDate>Tue, 30 Jan 2007 08:50:36 -0800</pubDate>
</item>
<item>
<title>New Documentation Section</title>
<link>http://swaret.sourceforge.net/Article6.html</link>
<description>I've added a wiki module to create documentation for swaret (man pages, etc).  The link can be found here.  This soon will be located on the menu under &quot;Documentation&quot;.
Update:  the wiki for swaret can be found at http://swaret.wiki.sourceforge.net.</description>
<pubDate>Fri, 15 Dec 2006 13:37:17 -0800</pubDate>
</item>
<item>
<title>Article about swaret</title>
<link>http://swaret.sourceforge.net/Article5.html</link>
<description>Was reading Linux Weekly News, and they pointed to an article about swaret at http://www.linux.com/article.pl?sid=06/10/12/1337224.  Most of the comments on the article I agree with, and when I stabilize the 2.0 branch I think that swaret will rate [good] on all counts.</description>
<pubDate>Thu,  2 Nov 2006 07:22:47 -0800</pubDate>
</item>
<item>
<title>Still Active</title>
<link>http://swaret.sourceforge.net/Article4.html</link>
<description>For those that are wondering, swaret is still active.  However, it is taking a back burner to other projects at my work, such as:
1) Getting SmartCard login to work with Linux (yes, it is working)
2) Evaluating MediaWiki for usability in scientific research
3) A dozen other things (small, but they don't go away)

I've uploaded into the download section the latest test branch.  It is writen in PERL, and is about 75% of the way to a stable release.  Soon, swaret will be a 100% replacement for pkgtools (that is my goal).</description>
<pubDate>Mon, 30 Oct 2006 06:02:15 -0800</pubDate>
</item>
<item>
<title>Chance to be famous</title>
<link>http://swaret.sourceforge.net/Article2.html</link>
<description>Currently PostNuke does not have the ability to e-mail people when hosted on a site like Sourceforge, which has turned off sendmail and does not allow connecting to SMTP servers.  What sourceforge does allow is sending the e-mail to the database server, then having a cron job take that information and send out via the mail command.
What is needed is someone to extend the class.phpmailer.php to allow sending to a mysql database.  I don't think it has that ability.  I don't have time, but there are a lot of projects that would be served by this.  Just a thought.</description>
<pubDate>Thu, 29 Jun 2006 13:32:54 -0700</pubDate>
</item>
<item>
<title>Resubmit Open Issues</title>
<link>http://swaret.sourceforge.net/Article1.html</link>
<description>I am unsure if the fields from the old version of PostNuke are the same as the new.  In the interest of all concerned, please resubmit any outstanding issues that you may have in the forums.  This can be about any slackware issues as well.</description>
<pubDate>Tue, 27 Jun 2006 18:11:29 -0700</pubDate>
</item>
</channel>
</rss>
