octave port group: Remove orphaned paths

[Schamschula (Marius Schamschula)]

When upgrading/deactivating/removing octave packages octave paths for the removed paths remain behind. Octave warns the user of these. For example:

warning: load_path: /opt/local/lib/octave/packages/interval-1.2.0/x86_64-apple-darwin13.4.0-api-v50+: No such file or directory
warning: load_path: /opt/local/share/octave/packages/interval-1.2.0: No such file or directory
warning: load_path: /opt/local/lib/octave/packages/io-2.2.11/x86_64-apple-darwin13.4.0-api-v50+: No such file or directory
warning: load_path: /opt/local/share/octave/packages/io-2.2.11: No such file or directory
warning: load_path: /opt/local/lib/octave/packages/tsa-4.3.2/x86_64-apple-darwin13.4.0-api-v50+: No such file or directory
warning: load_path: /opt/local/share/octave/packages/tsa-4.3.2: No such file or directory

Use the octave rmpath command to remove these.

[michaelld (Michael Dickens)]

where and how do I use this command in the PortGroup?

[Schamschula (Marius Schamschula)]

I was hoping you knew…

The octave port group is rather nebulous to me - starting with the fact the the build happens in the configure stage, and so on.

That being said, this needs to happen in the post-deactivate stage. The main trick will be to figure out which directories need to be deleted and then sending the appropriate system call, i.e. something like

system "${prefix}/bin/octave-cli -q -f --eval 'rmpath(\"/path/to/directory\")'"

My escapes may not be correct, i.e. untested, but you get the idea.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

In 5c63c970/macports-ports:

octave and packages: update version 4.0.3 -> 4.2.0

upgrading octave necessitated rebuilding every octave package,
so take this opportunity to fix some longstanding issues.

Fixes #52917
Fixes #50261
Fixes #50262
Fixes #52255
Fixes #51670