<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/nativeoberon/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/nativeoberon/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 27 Feb 2003 20:50:57 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/nativeoberon/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Working sf-based build</title><link>https://sourceforge.net/p/nativeoberon/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Being a simple system, the Native Oberon build tool &lt;br /&gt;
consists of a single Oberon text with some commands for &lt;br /&gt;
building the system from the local file system.  For &lt;br /&gt;
distributed development via sf.net, a CVS-based build &lt;br /&gt;
process would make sense, with a CVS repository on &lt;br /&gt;
sf.net.  This is problematic, since Oberon does not &lt;br /&gt;
currently have a CVS client.  To get going as quickly as &lt;br /&gt;
possible, one way of working around the problem would &lt;br /&gt;
be to use an external CVS client running on another OS, &lt;br /&gt;
and export/import the files on the Oberon file system, &lt;br /&gt;
converting from Oberon text documents to plain ASCII &lt;br /&gt;
along the way.  Of course this would only be an interim &lt;br /&gt;
solution, and true CVS client for Oberon would be a later &lt;br /&gt;
improvement.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pieter Muller</dc:creator><pubDate>Thu, 27 Feb 2003 20:50:57 -0000</pubDate><guid>https://sourceforge.net5c8a6d580f59a170ac24267fbdc6c01264bad17f</guid></item></channel></rss>