On 19 Aug 2015, at 11:04, Fabrice Le Fessant <[email protected]> wrote: > > On Wed, Aug 19, 2015 at 11:56 AM, Louis Gesbert > <[email protected]> wrote: >>> package, preventing "opam-cache", etc.), either to reserve names for >>> possible plugins ("search", "file", "git", etc). >> >> "search" is already an opam command :) > > Is it planned to have a dynlink mechanism for plugins ? Then, it would > be possible to override existing builtin commands from inside. > Another possibility would be to have aliases for builtins, and allow > to override their default names: for example, if I type "opam search > XXX", opam would first call "opam-search", and only if it does not > exist, call the builtin. Then "opam-search" would be able to call > "opam builtins search XXX" to access the builtin command with enhanced > parameters... >
Do you have a use-case in mind for this? -anil _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
