At the advise of the Guardians (of gretl), I share the following incident with the community, just in case somebody encounters the same.

I run gretl 2023b (x86_64, gkt2) build date 2023-07-21.

I recently upgraded (so to speak) my laptop from Windows 7 to Windows 10 (both 64bit). Maybe this has something to do with the following?

Yesterday I decided to install the new frontier 1.1 function package: open gretl session, go to File/function packages/on server..., select the package, was asked to install, said yes, installation done.

Then I went to the local machine list of function packages -and there I saw both frontier 1.0 and frontier 1.1. So the installation did not automatically replaced frontier 1.0. 

But the problem was, selecting frontier 1.1 and running it resulted in running frontier 1.0.

Moreover, selecting, from the local machine list, the frontier 1.0 package and asking to delete/remove it, resulted in a message "This cannot be done/failed"...

After some digging, this is what I found:

The older frontier 1.0 package folder was in a C:\ProgramFiles\gretl\functions folder together with other gretl functions  like dbnomics, geoplot, extra, etc.

But the new frontier folder 1.1 was, in another folder   C:\Users\[user name]\AppData\Roaming\gretl\functions

There were no duplicates in the two folders. In the second there was, for example the "StrucTiSM" package (which I hadn't installed myself).

The forced remedy of the specific  situation was to delete directly the frontier 1.0 package folder from its source location. After that, it disappeared from the local machine list of functions, and frontier 1.1 executed no problem.

As a test, I installed also another package, and it too went in C:\Users\[user name]\AppData\Roaming\gretl\functions, where frontier 1.1 resides.

-- 
Alecos Papadopoulos PhD
Affiliate Researcher
Dpt of Economics, Athens University of Economics and Business
Foundation for Economic and Industrial Research (IOBE)
web: alecospapadopoulos.wordpress.com/
ORCID:0000-0003-2441-4550