[Pkg-octave-devel] Bug#691311: Bug#691311: Bug#691311: Bug#691311: error: feval: function `unimplemented' not found

Jordi Gutiérrez Hermoso jordigh at octave.org
Thu Oct 25 20:56:39 UTC 2012


On 25 October 2012 16:20, Thomas Weber <tweber at debian.org> wrote:
> On Wed, Oct 24, 2012 at 12:17:01PM -0400, Jordi Gutiérrez Hermoso wrote:
>> On 24 October 2012 08:17, Mike Miller <mtmiller at ieee.org> wrote:
>> > The octave package provides the directories, and liboctinterp.so.1 has
>> > a compiled-in set of paths with its version number that it attempts to
>> > load.
>>
>> Ah, this is probably not the greatest idea ever. I'm not sure how to
>> fix it. Provide a build-time option for setting this path? Setting the
>> path by default to a versionless path?
>
> I'd just remove the version from the path, but this raises the question
> of what is achieved by having the version number in the path in the
> first place.

I'm CC'ing the Octave list. Not sure what's going on here, re Debian
bug #691311:

    http://bugs.debian.org/691311

My guess is that it's just cruft from old times. We didn't try to keep
API compatibility in liboctave until recently, so without that it made
more sense to put the Octave version in the path.

- Jordi G. H.



More information about the Pkg-octave-devel mailing list