#1 Working sf-based build

[Pieter Muller]

Being a simple system, the Native Oberon build tool
consists of a single Oberon text with some commands for
building the system from the local file system. For
distributed development via sf.net, a CVS-based build
process would make sense, with a CVS repository on
sf.net. This is problematic, since Oberon does not
currently have a CVS client. To get going as quickly as
possible, one way of working around the problem would
be to use an external CVS client running on another OS,
and export/import the files on the Oberon file system,
converting from Oberon text documents to plain ASCII
along the way. Of course this would only be an interim
solution, and true CVS client for Oberon would be a later
improvement.