Saturday, 6 April 2024

[netsurf-users] Re: 6696 fails to start on RISC OS

In article <0650874d5b.John@rickman.argonet.co.uk>,
John Rickman <rickman@argonet.co.uk> wrote:
> In message <g4wacql5n6npzdrjcgdjuslz7kvokfjqyh3gwky6cwywkgbvr7@5le2zo43v3z7>
> Rob Kendrick <rjek@rjek.com> wrote:

> > 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 nights RISC OS coding zoom meeting there was discussion of
> this SocketWatch issue and I was asked to write to this list
> seeking some information. 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.

That is NOT the way to go!

The correct way is that the latest version should be used everywhere,
and the old ones removed (as long as the later fixed version has no
incompatible API changes).

Please see the long list of changes made since v0.04y (02-12-2002)
that are included in v0.07 (11-01-2019) some 16 years later.

Other applications may rely on some of those fixes and changes!

The latest v0.07 AFAIK is available at https://www.aconet.nl/tools/

Martin

No comments:

Post a Comment