Re: pkg problems

[Sergei Steshenko]

----- Original Message -----
> From: Terry Duell <address@hidden>
> To: address@hidden
> Cc: 
> Sent: Sunday, November 25, 2012 2:26 AM
> Subject: Re: pkg problems
> 
> Hello All,
> 
> Sorry to keep on with pkg issues, but just as one problem is fixed another 
> arises.
> 
> I find that some of my recently installed packages via 'pkg install -forge 
> xxx' are shown as not loaded when I run 'pkg list'.
> When I run, for example, 'pkg load signal', 'pkg list' shows 
> that signal is loaded, but a 'help pwelch' returns 'error: help: 
> `pwelch' not found'.
> If, after running 'pkg load signal' I run 'savepath', the 
> problem still persists, and 'path' returns...
> 
> /home/terry/octave/signal-1.2.0/x86_64-redhat-linux-gnu-api-v48+
> 
> as the only entry for signal.
> If I manually run 'addpath 
> ("/home/terry/octave/signal-1.2.0")', the 'help pwelch' 
> works as expected.
> 
> Am I now seeing more pkg bugs, or are this behaviour due to me going about 
> things in the wrong way?
> 
> Cheers,
> --Regards,
> Terry Duell
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave
>

'pkg.m' in particular is hopelessly broken; Octave packaging in general is 
_not_ spec'ed.

As simple as that.

I have my own version of 'pkg.m' (which I published to the list), and I build 
_all_ the packages I can from scratch, both global and local, and they are all 
autoloaded in my case, and if a package interferes with what I need to do, I 
explicitly unload it in my script.

Regards,
  Sergei.