For background, quoting Rob Kendrick:
> My /guess/ is that SocketWatch (or similar) is running via an
> application launched at boot and it is an earlier version than NetSurf
> requires, so NetSurf's !Run's RMEnsure tries to replace it with a newer
> version?
At last Saturday nights RISC OS coding zoom meeting there was discussion
of this SocketWatch issue and John Rickman was asked to write to this
list seeking some information. (He's only subscribed to ns-users, so
I've taken over the task.) We looked at the change log for v0.07 and
tested the latest NetSurf against v0.04. It appeared to run without
problems.
Would you be willing in the short term to RMensure against v0.04 instead
of v0.07. This would avoid some breakage and people having to change
their run files.
This is significant only because older/current versions of SocketWatch
cannot be replaced "live" as they are in use. Thus simply RMensuring a
newer version will fail.
R-Comp have already confirmed that they will QA this new version with
their software and update as necessary. The upgrades won't, of course,
help those who don't/won't upgrate directly.
The documentation provided with 0.07 specifically says that it is an
unofficial release. The last "official" release seems to have been
0.04. Is it wise to force people to update their master !System with
an unofficial release?
Surely better to RMensure the official version if it works as expected.
(The changelog shows no functional/API changes since 0.04). By all means
include 0.07 in your zip, but use "RMensure" they way it was designed -
to specify the minimum version the will function with your software.
David
No comments:
Post a Comment