On Mon, 25 Mar 2013, Riccardo (Jack) Lucchetti wrote:
On Mon, 25 Mar 2013, Riccardo (Jack) Lucchetti wrote:
> On Mon, 25 Mar 2013, Lee Adkins wrote:
>
>> Here is an unexpected feature I encountered in gig. [...]
>
> Sorry, Lee. I have to correct you on your grossly inappropriate choice of
> words. This is not an unexpected feature. This is a Bug, with a capital B.
>
> I'll try to fix it asap. Sorry, folks.
It should be ok now. Allin: I've updated the gig gfn file on ricardo and the
zip file on sourceforge. Does this mean that people should be now
automagically notified of the update when the choose the gig menu entry in
the GUI client?
Urgh, this is a bit complicated.
First, I was forgetting about the need to update addons.xml.
That file is generated at the top level of the gretl-addons
source tree, via "make addons.xml". It then has to be synced
to
<user>,gretl@web.sourceforge.net:/home/project-web/gretl/htdocs/addons-data/
This should be done whenever there's a version-number change
for any of the addons in CVS.
With that update in place on the server, if the user goes to
"/Help/Check for addons" in the gretl GUI, he/she will get a
notification that there's a gig update available.
So at present it's not totally automagic: you have to use
"Check for addons".
Allin