Re: package manager patch + problem

[Paul Kienzle]

On Feb 27, 2007, at 3:21 PM, Michael Goffioul wrote:

> > what does
> >
> > pkg unload <pkg>
> > clear all;
> > pkg uninstall <pkg>
> >
> > do? Perhaps the clear all isn't needed, but might be.. I think there 
> > are
> > also some packages in octave-forge that cheat and use "mlock" to 
> > prevent
> > the files being removed, and I don't know how that will work..
>
> "clear all" should be enough. Locked files shouldn't
> be a problem for m-files. I don't know if it's possible
> to lock an oct-file, but if yes, then it might be problem;

Yes, because if you have variables of a user-defined type
octave will segfault when you access them.

> however, I guess the file is only locked when the code is
> actually executed; so by restarting octave and then "pkg
> uninstall", it should be OK.

Looking at autoload(), it doesn't seem to load the file.
I suspect the which() command does, but it is not
immediately clear from glancing at the code.  Maybe
we could use the following instead:

        autoload("glog",file_in_loadpath("gf.oct"))


- Paul