On Wed, 5 Dec 2018, Sven Schreiber wrote:
Am 04.12.2018 um 23:43 schrieb Allin Cottrell:
> On Tue, 4 Dec 2018, Sven Schreiber wrote:
>
>> 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.
OK, but if it is "only" installed and not include-ed automatically, where do
I put the "include" statements?
You didn't quote the last part of my statement, namely
<quote>
And if a script does "include <yourpkg>" we'll try to include the
dependencies first, if they're not already in memory.
</quote>
So if package A depends on package B, then "include A.gfn" (in any
regular script that calls functions from A) automatically implies
"include B.gfn".
Allin