help-octave
[Top][All Lists]
Advanced

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

Re: pkg problems


From: Juan Pablo Carbajal
Subject: Re: pkg problems
Date: Sun, 25 Nov 2012 13:25:55 +0100

On Sun, Nov 25, 2012 at 6:42 AM, Terry Duell <address@hidden> wrote:
> On Sun, 25 Nov 2012 16:27:12 +1100, Carnë Draug <address@hidden>
> wrote:
>
>>> OK, I removed the addpath for all the above packages, then ran 'pkg load
>>> signal', and 'help pwelch' now runs as expected, so this may have put
>>> things  in a bit better shape. It will take a bit of time to test/check it
>>> all
>>> properly, but at least it is looking a better than it was.
>>
>>
>> My guess is that one of the packages you installed is messing up your
>> paths somehow. Try loading and unloading them, checking signal in
>> between, until you find the culprit. This is one of the reasons
>> packages are no longer autoloaded. Some of them can break your Octave.
>>
>> I'd recommend you to install packages with the -noauto option to
>> overwrite any autoload settings a package may have. For the ones you
>> already have installed you can change it with "pkg rebuild -noauto
>> all". And you can also add a "pkg unload all" on the top of your
>> .octaverc, and only then, load the packages you need.
>
>
> At this stage it does appear to be OK. I have edited my .octaverc file to
> load the packages, and testing a few functions from a sample of packages
> shows no problems.
> I don't have the time to fully test everything right now, but when time is
> available I will run through a more rigorous test and run "pkg rebuild
> -noauto all" .
>
> Thanks for all your help. This little exercise has documented the problem
> for any others who may be unfortunate enough to experience it.
>
>
> Cheers,
> --
> Regards,
> Terry Duell
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave

Terry,

since the paths were hardcoded it may be that you installed a new
version of the package and the paths got messed up. Try to avoid
hardcoding paths to the packages since the folde rthat contains the
may change name with updates.
As Carnë suggested, use the pkg action "load" in your octaverc instead.

Cheers


reply via email to

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