#47478: octave-stk @2.2.0_0: update to 2.2.1 -----------------------------+--------------------------------- Reporter: mschamschula@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch maintainer Port: octave-stk | -----------------------------+--------------------------------- Comment (by mschamschula@…): Replying to [comment:5 michaelld@…]:
Interesting. I did some sleuthing just now & confirm your finding / belief. What seems to be happening is that the "post-deactivate" and "post-activate" hooks in the octave-1.0 PortGroup are not quite working -- they leave behind cruft (or, rather, something is leaving behind cruft in /opt/local/lib/octave/packages and /opt/local/share/octave/packages, maybe elsewhere). And, that cruft is, for some reason, being found ahead of the actual pkg contents. So, for example, if you never had octave-stk installed then -any- version should work; if anything prior to 2.2.0 was installed, then there is cruft hanging around which tries to do the load & fails because the octave load paths are not correct. When I remove this cruft, all is well again. I'm just not sure why there is cruft yet. I'll look into those hooks & see what I can figure out. Cruft happens :)
Apropos cruft: After uninstalling octave-stk a couple of directories remain in the path sea. I had to manually remove them using rmpath. -- Ticket URL: <https://trac.macports.org/ticket/47478#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X