Following the gretl 2020a release, I've put up a variant package for
macOS (>= 10.6) at
(note: it's not on sourceforge at this point). This version
announces itself as 2020b-git but its content is exactly the same as
2020a. Only the initialization is changed to make it more compatible
with Apple's new security model.
Clicking on the Gretl.app icon invokes a bash script
/Applications/Gretl.app/Contents/MacOS/gretl.sh which sets up the
environment and calls "real gretl" at
Clicking on the Gretl.app icon invokes "real gretl" at
/Applications/Gretl.app/Contents/MacOS/gretl, with the environment
setup now internalized in C code.
Under the new scheme, if you wish to start gretl from a Terminal
window you should invoke
Hi Allin, if you can hold off the release for one more day I could
probably test the current situation of the windows build again, starting
from a clean environment. I know the relevant updates occurred with
2019d and not so much with 2020a, but I never properly re-checked
whether we have reached a working steady state.
But of course not super important, so if you already ran your test suite
etc. I'd say just go ahead.
The current macOS (1.015, Catalina) has additional security checks.
The installer gives a warning for the current gretl-2019d-quartz.pkg distribution.
Apple warns that the program cannot be run. There is however a button to open the file so it can be opened (at your own risk).
But it is not safe to assume that this will continue to be the case.
See this page: https://support.apple.com/en-gb/guide/security/welcome/1/web
As of February 2020 Apple will require that apps distributed outside of the Mac store will have to be notarized.
which most likely means that the current gretl package can't be opened and that gretl cannot be run on macOS Catalina.
Another remark: I do not know how the macOS package is created but the contents cannot be inspected by Pacifist (an app used to view the contents of a ,pkg distribution; see https://charlessoft.com). Very useful app.
for the first time I am working with gretl's ODBC connector. So far it
seems to work fine for standard queries using the Exasol data base on
linux. However, I stumbled over to 2 issues:
1) I want to write a open_odbc_connection() function. Unfortunately, the
'open' command cannot be executed within a function. For its standard
application loading a data set I fully understand the reason. However,
for just opening a ODBC connection by the '--odbc" option, I don't get
rational for this restriction.
Feature request: Allow making use of the open command in case the --odbc
option is passed.
2) While loading data through the 'data' command, e.g. by executing
<data x query="@statement" --odbc>, this command does not seem to work
in case one wants to send a 'statement' -- like "create table" or "drop
table" -- to the database which does not return a series.
Feature request: allow sending a sql-statement which does not return a
series or anything.
Maybe these points imply to add a new command or function. What do you