On Thu, 13 Feb 2020, Sven Schreiber wrote:
Am 13.02.2020 um 14:18 schrieb Allin Cottrell:
> On Thu, 13 Feb 2020, Sven Schreiber wrote:
> Yes. And it's also the arena from which the current versions of addons
> are downloaded (via the "Check for addons" dialog).
> This reminds me of something I need to look into: do we currently
> block download/installation of (non-addon) packages that require a
> gretl version higher than the running gretl instance? (We should, but
> I'm not sure we do.)
If you didn't implement it recently, I don't think this is already done.
Actually, after checking, it seems we should be OK. When you try to
install a package via the GUI gretl sends its version info to the
server, and the server declines, with the message "<package>
<version requires gretl <version>" if the gretl version requirement
is not met.
I tested that by faking my current gretl as 1.10.1, and I got the
expected error message when I attempted to install DiebMar 1.3,
which wants gretl 2019a.
However, I did find a bug in this area: if you went to packages on
the server and tried to get "Info" on a package with a higher gretl
requirement, you got a kinda broken-looking error message from
libxml (because the downloaded material was not XML, rather the
plain text error message just described). That's now fixed in git.
There's a separate mechanism for delivering an error message if you
try to download an addon that doesn't have a version compatible with
your gretl version.