Re: [Gretl-devel] Function packages on Windows: new path permanently added
On Thu, 11 Oct 2018, Allin Cottrell wrote:
On Sat, 6 Oct 2018, Sven Schreiber wrote:
> I'm noticing that with the Oct 4th snapshot in the (local)
> function package list window a (preliminary) package appears that
> lives in a non-standard path.
>
> This is new I think, because it used to be that one could switch
> to a user-specified path, and then only those packages from there
> was shown. If one reverted to the standard listing, the
> non-standard paths would be forgotten again.
>
> Is this a bug or a feature?
Sorry it has taken a while, but anyway... I don't think this has
changed lately. When gretl is asked to show function packages "on
the local machine" we search in the following locations:
* the "system" functions directory, which will be under /usr on
Linux (possibly /usr/local if self-compiled), /Program files/gretl
on Windows;
* the "functions" subdirectory of the user's "dotdir" (which is
where packages will go on "install" if the user doesn't have write
permission on the "system" directory); and
* the user's current working directory.
Another thought, in response to Sven's "bug or feature" question.
The inclusion of the user's working directory in the package search
path is a feature in the sense of being deliberately designed in,
but maybe it's a mis-feature (aka bug). Since you probably spend
more time working with function-package files than anyone else,
Sven, I'd value your opinion on whether including the working
directory by default is a help or a hazard. It would be easy enough
to exclude it.
Allin