[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pkg problems

From: Carnë Draug
Subject: Re: pkg problems
Date: Sun, 25 Nov 2012 03:54:28 +0100

On 25 November 2012 03:34, Terry Duell <address@hidden> wrote:
> On Sun, 25 Nov 2012 12:44:39 +1100, Carnë Draug <address@hidden>
> wrote:
>> On 25 November 2012 01:26, Terry Duell <address@hidden> wrote:
>>> 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?
>> Packages are no longer automatically loaded. You have to load them
>> yourself. But you keep mentioning stuff from your .octaverc. Can you
>> show us what do you have there?
> Sure, below is a copy of my .octaverc.
> Following on from my previous post (above), you will see
> '/home/terry/octave/signal-1.2.0', which, as I said,  I had to add manually.
> But to return to my question, after originally loading signal, and running
> savepath, Octave still didn't know about signal functions until I manually
> added the signal path.
> ----------~/.octaverc-------------------
> ## Begin savepath auto-created section, do not edit
>   addpath
> ('/home/terry/octave/image-2.0.0/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/signal-1.2.0/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/optim-1.2.2/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/linear-algebra-2.2.0/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/specfun-1.1.0/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/miscellaneous-1.2.0/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/general-1.3.2/x86_64-redhat-linux-gnu-api-v48+:/home/terry/Myoctave:/home/terry/octave:/home/terry/octave/struct-1.0.10/packinfo:/home/terry/octave/struct-1.0.10/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/gnuplot-1.0.1/packinfo:/home/terry/octave/odepkg-0.8.2/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/java-1.2.9/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/control-2.4.1/x86_64-redhat-linux-gnu-api-v48+:/home/terry/octave/io-1.0.20/x86_64-redhat-linux-gnu-api-v48+',
> '-begin');
> ## End savepath auto-created section

The fact that you needed to addpath manually already suggests that
there's something wrong. You should have "pkg load" and "unload" take
care of the paths for you. What packages have you installed? What does
"pkg list" shows? Remove (or comment out) that addpath line from your
octaverc, start Octave again, and load the signal package only. Do you
have a problem accessing its functions? Also, I know Debian has a file
in /etc/octave.conf that used to mess up with my pkg. Does Fedora also
has one (maybe in some other place)?

> If packages no longer auto load, what is the recommended method of doing so,
> such that they are always loaded when octave is started,

For packages you want to load automatically at startup, the
recommended way is to add a "pkg load pkgname" in your .octaverc file.
You can have multiple in one line "pkg load pkgname1 pkgnam2
pkgname3". For packages ones you don't want to load automatically, do
nothing, and load them only whenever you need them.

> and the paths are saved in the .octaverc file?

Paths for packages are not be saved in .octaverc. pkg does not touches
your .octaverc file. It has another file with the list of packages and
their paths and adds and removes them to your search path when you
load and unload a package.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]