On Tue, 4 Dec 2018, Sven Schreiber wrote:
Am 02.12.2018 um 10:08 schrieb Sven Schreiber:
> Am 02.12.18 um 00:55 schrieb Allin Cottrell:
>>> "parasitic" GUI-oriented package which depends on SVAR. I think
you're
>>> right in saying that wouldn't require changes in core gretl; anyway,
>>> running the experiment would be worthwhile.
>>
>
> OK, I'll try that. (Not today.)
Ahem, turns out I can't find any information on how to make a package depend
on another one...
I see some "depends" field/entry in the gretlfunc.dtd, but it's not clear
to
me what this implies for the packaging.
OK, this is not yet documented in the Function package guide (I
think, because it hasn't yet been officially ratified, if we can
attach any meaning to that expression). But it's pretty simple: you
can state in the .spec file, or via the current package-maker GUI
(under "Extra properties") that your package depends on one or more
other packages. In spec file syntax that would be:
depends = <space separated names of packages, without their
".gfn" or ".zip" extensions>
The consequence is that if somebody tries to install your package,
gretl will try to install the stated dependencies first. And if a
script does "include <yourpkg>" we'll try to include the
dependencies first, if they're not already in memory.
Allin