4:41 a.m.
Hi,
not too long ago we had a thread about what happens (on Windows) when
function packages should be deleted. Now gretl reports an informative
error message (you don't have the permissions to remove it, or sth. like
that).
However, there still is a problem for example when packages have been
retired, so they do not exist on the server anymore. They have been
installed under gretl, but they cannot be locally removed again.
This is a bit awkward because if a newer version exists (so the package
is not retired, but updated on the server) overwriting is possible
without any problem.
So why is overwriting OK permission-wise, but deleting is not?
And to give a concrete example, one of those reorganized and retired
packages was LOGIT_HETERO.gfn by Artur.
thanks
sven
1:49 p.m.
On Fri, 22 Mar 2019, Sven Schreiber wrote:
not too long ago we had a thread about what happens (on Windows)
when
function packages should be deleted. Now gretl reports an informative
error message (you don't have the permissions to remove it, or sth. like
that).
However, there still is a problem for example when packages have been
retired, so they do not exist on the server anymore. They have been
installed under gretl, but they cannot be locally removed again.
The Inno installer used by gretl_install.exe manages to escalate
permissions (if possible) when installing under "/Program Files".
Anything installed in that way can be removed by running the Inno
uninstall program. So I don't think there's really a "cannot be
removed" condition, in a strong sense.
If a user doesn't have write permission for Program Files (without
escalation) then an updated function package, installed independently
of gretl_install and Inno, will go into the user's filespace where
there shouldn't be a problem with removing it.
This is a bit awkward because if a newer version exists (so the
package
is not retired, but updated on the server) overwriting is possible
without any problem.
So why is overwriting OK permission-wise, but deleting is not?
It's OK to install a newer version of a package into one's personal
filespace. This won't overwrite an older version installed via
gretl_install, but it'll take precedence. If actual overwriting is
possible than deletion would also be possible.
Allin
2:27 p.m.
Am 22.03.2019 um 18:49 schrieb Allin Cottrell:
On Fri, 22 Mar 2019, Sven Schreiber wrote:
>
> So why is overwriting OK permission-wise, but deleting is not?
It's OK to install a newer version of a package into one's personal
filespace. This won't overwrite an older version installed via
gretl_install, but it'll take precedence. If actual overwriting is
possible than deletion would also be possible.
Right, I see.
However, the gretl installer doesn't install contributed packages (with
a few exceptions, perhaps), right? So the question is, where did the
packages come from, and ended up in a place from which now they cannot
be deleted anymore? I cannot rule out that in the past I have done some
funny things with permissions and stuff, but I'll keep an eye open.
thanks
sven
2067
days inactive
2067
days old
2 comments
2 participants
participants (2)
-
Allin Cottrell -
Sven Schreiber