Ollie Clark <[email protected]> wrote: > 2009/11/11 Jeremy Nicoll - roinfo <[email protected]>: > > Ollie Clark <[email protected]> wrote: > > > >> I don't think it's as simple as that. Part of the installation is > >> installing the ROM images in the right place but they can't be > >> included in the distribution so it really depends on how and where the > >> user has got them from. > > > > ?? I said nothing about rom images. The OP said he'd mistyped: > > I know, I was just thinking for a simple installation you don't really > want to make the user go off and find ROM images and then copy them > somewhere inside rpcemu. Then again that's what the Spoon edition does > in Windows.
That's because of copyright on the ROM code, isn't it? > > > sudo apt-get install build-essential subversion liballegro4.2 > > liballegro4.2-dev liballegro4.2-plugin-jack unzip wget > > > > Surely that could go into a one-line script? > > Probably, except that most stages in the installation instructions > involve you checking it worked. And how does a one-line script interfere with that? I'm not suggesting a full-blown script, just something that already contains single-line commands like the one above. It'd be terribly easy to get a command like that wrong. > At least with the manual instructions you can post to a newsgroup or > mailing list: > > I've done A and that worked, then B and that worked, then C and I got > this error message. HELP! But when you typed the commands manually, unless you c&p the actual commands you typed into your pleas for help, youll very likely get the plea subtlely wrong, especially of the problems are due to the commands being wrong. OTOH if you can say: I did ./CLI03 then ./CLI04 then ./CLI05 ... at least everyone will know that you ran the commands that were provided. > I don't know though, if people are just blindly typing stuff from the > instructions without actually reading the results or checking it's > worked there may as well be a script. It's just not the Linux way. You > either do it in a package or do it manually, preferably with some > compilation. :-) It's also a separate argument. > > One reason for doing so would be that if & when the versions of each of > > those packages or libraries or whatever they are change - which I'd > > expect the people who design rpcemu would know, they could change the > > script as well. > > Well, I guess that would be nice if there's someone willing to do it. If there isn't anyone willing to do it, that begs the question of who's keeping the instucttions that the OP was using uptodate. Or do you think that total beginners following incorrect instructions are going to enjoy the experience? But .. but .. it's the true linux way! > That someone's not me (I'm perfectly happy doing the CLI dance). But how do YOU know precisely what to put in each command? > It's presumably not you either. I know less than Dave Symes about building/installing rpcemu, but have a lot of experience, though not recently, of assembling & linking another OS from scratch. So not me. > Who are you tasking with this? And are you sure they're willing? :-) Who maintains the current instructions? -- Jeremy C B Nicoll - my opinions are my own. _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
