Re: macOS 4.4.0 DMG (beta2) ready for testing

[apjanke-floss]

Hi, Mohammed,

I think I have a fix for this now.

It looks like packages that have compiled components cannot be shared
between Octaves that are installed at different paths, because their dylib
links include the full path to the liboct and liboctinterp they were linked
against.

So, I think your issue is that your control package was built and installed
by a different Octave, so it's incompatible with the Octave.app that lives
at a different path.

To fix this, I've modified Octave.app to store its packages in a separate,
versioned directory.

The downside is that you'll have to reinstall all your packages with each
Octave.app version upgrade. The upside is that your Octave won't crash. I
think it's worth the tradeoff.

If you have a chance, please download the new Octave.app 4.4.0 beta5 build
and see if that works for you. When you install and run it, you should see
no packages installed under "pkg list", but a "pkg install -forge control"
should succeed, and should not interfere with the packages installed under
your other Octave installations.

https://github.com/octave-app/octave-app/releases/download/v4.4.0-beta5/Octave-4.4.0-beta5.dmg

References:
http://lists.gnu.org/archive/html/octave-maintainers/2018-07/msg00101.html
https://github.com/octave-app/octave-app-bundler/issues/42
https://github.com/octave-app/octave-app-bundler/commit/ee0c5a38469d4c9ed9c82dc1b0edd8637debcf45

Cheers,
Andrew



--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html