You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In other languages specific package managers (Python's pip and distutils system) it is possible to directly build extensions to the language as part of the package installation process. Octave has a package system that allows a similar functionality.
To achieve something similar with mpm, we might intoduce one or more optional .m files which live at a special location relative to the package root. These files implement hooks that are run at the build, install, and uninstall steps. The package maintainer would write hooks and distribute them as part of the package. If a hook is not implemented, mpm would just skip that step.
For example, a build hook might consist of a few calls to mex ...
mex myFile.c -myFlags
In the Octave system, it's possible to run a ./configure script at build time to resolve any system specific include paths and flags.
The hooks get copied over to a package-specific metadata directory by mpm. Then at uninstall time, mpm runs the copy of the uninstall hook cached in the metadata directory before wiping it clean.
The text was updated successfully, but these errors were encountered:
This checks for files install.m when running mpm install _, and uninstall.m when running mpm uninstall _. (Confirms with user before running, unless --force is set.)
In other languages specific package managers (Python's
pip
anddistutils
system) it is possible to directly build extensions to the language as part of the package installation process. Octave has a package system that allows a similar functionality.To achieve something similar with
mpm
, we might intoduce one or more optional.m
files which live at a special location relative to the package root. These files implement hooks that are run at the build, install, and uninstall steps. The package maintainer would write hooks and distribute them as part of the package. If a hook is not implemented,mpm
would just skip that step.For example, a build hook might consist of a few calls to
mex
...In the Octave system, it's possible to run a
./configure
script at build time to resolve any system specific include paths and flags.The hooks get copied over to a package-specific metadata directory by
mpm
. Then at uninstall time,mpm
runs the copy of the uninstall hook cached in the metadata directory before wiping it clean.The text was updated successfully, but these errors were encountered: