Opened 15 years ago

Closed 15 years ago

Last modified 17 months ago

#8444 closed patch

RISC OS port information

Reported by: SF/pnaulls Owned by: fingolfin
Priority: normal Component: Port: RISC OS
Keywords: Cc:
Game:

Description

On http://scummvm.sf.net/links.php. the link to the RiscOS (sic) port should be updated. It should point to my RISC OS 0.80 port which was released last year, and is at http://www.riscos.info/unix/

The RISC OS port is "official" inasmuch as there's no additional patches required beyond the minor ones attached. One is a spelling fix, the other is a change to the configure script because of a change in the RISC OS tools.

Ticket imported from: #1234668. Ticket imported from: patches/549.

Attachments (2)

configure.p (1.1 KB ) - added by SF/pnaulls 15 years ago.
Configure patch
logic.p (537 bytes ) - added by SF/pnaulls 15 years ago.
Spelling mistake patch

Download all attachments as: .zip

Change History (10)

by SF/pnaulls, 15 years ago

Attachment: configure.p added

Configure patch

by SF/pnaulls, 15 years ago

Attachment: logic.p added

Spelling mistake patch

comment:1 by fingolfin, 15 years ago

There is no ScummVM 0.8.0. So you have packaged a CVS version and are distributing it, labeled as if it was a point release. Very bad, please change that.

Furthermore, it's still not official, since so far, neither you nor the the other guy have made any efforts to contact us, inform us about the port; so your package most definitly is inofficial.

We could try to change that, of course; this tracker item (which I have moved to the patch tracker now) would be a first step.

comment:2 by SF/pnaulls, 15 years ago

Sadly, neither of your comments are true.

Yes, I have the version number wrong, sorry for that. It's really 0.7.0; and it's no accident it was released on Xmas day. Fortunately, the autobuilder for the ports now takes care of ensuring things are properly versioned.

As for telling you about it, I can assure you I made a great deal of effort to do so, including spending a couple of weeks last year in your IRC channel (it was conversations here that resulted in confusin over the version number), and previously submitting patches for the RISC OS version and informing people of my release.
Comments like this are patronising and don't really encourage further effort. It's because little was done the first time around that I made this report.

As for the "other guy", David McEwan is extremely busy and is unlikely to be easily contactable, but he is well aware that my port is newer than his.

comment:3 by fingolfin, 15 years ago

I am glad to hear your package is really 0.7.0 and not a CVS build. I hope your package system will be updated to reflect the correct version number eventually.

The IRC channel is a great place to develop ScummVM, discuss code changes, etc.. It is by no means an "official" contact point for ScummVM, though; in the end, using the mailing list, filing a tracker item, or contacting the lead devs is the way to go if you want to get a new port "officially" supported. Talking about it on IRC has the big drawback that only whoever happesn to be in the channel by chance will know about the conversation, hence it can't be considered "official" (which would imply that all team members know about it etc.). I don't say that to annoy you, it simply reflects reality.

Anyway, I have inserted a link to your RISC OS port to our links page, and applied your two patches to CVS. We'd definitely be interested in an official RISC OS port; if you are in turn interested in maintaining that, feel free to contact us via our scummvm-devel mailing list, and we can discuss the details (we need somebody who is reachable and responsible for packaging new releases as they are made; also, we prefer hosting binaries ourselves; the only so far exception is the Debian package, which is 'official', too).

Thanks for your efforts!

comment:4 by fingolfin, 15 years ago

Owner: set to fingolfin
Status: newclosed

comment:5 by cyxx, 15 years ago

Just a small remark about the "spelling fix" in the queen code. The "bobs" term used in this comment was standing for "blitting objects"...

comment:6 by fingolfin, 15 years ago

Argh. Sorry, I should have checked this better before commiting. I'll undo it (unless you already have).

comment:7 by digitall, 17 months ago

Component: Ports

comment:8 by digitall, 17 months ago

Component: PortsPort: RISC OS
Note: See TracTickets for help on using tickets.