On Fri, Nov 13, 2009 at 10:07:58AM +0000, Ollie Clark wrote: > Anyone can easily update the instructions. You just click on Edit on > the page and start typing. It's a completely different proposition > putting scripts in the download.
The other difficulty, which RPCEmu mostly avoids by having a long list of typed commands, is that different Linux distros do things slightly differently - so files might be in different places, or called different things, or work in a slightly different way. At the moment we don't have the manpower to maintain a script for Fedora, a script for Debian, a script for Ubuntu, a script for SUSE 11, a script for SUSE 10, a script for MacOS 10.5, a script for MacOS 10.6, a script for FreeBSD etc etc. At the moment the tension for coders is between doing things to make RPCEmu easy to install, and major features like networking. Installation is something you have a headache with once, but networking is something you might use every day. So that's what tends to win. As with most RISC OS projects, RPCEmu is low on manpower. It's not advertised as a slick project because it's still a work-in-progress. Most commercial w-i-ps don't see the light of day until they're done, while with RPCEmu you can try it every step of the way. But it's not a level playing field to compare it with a fully released, charged-for product like VRPC. (I should mention that I haven't done any coding for a good while, so the views above are my own only) Theo _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
