> - Fabrice Le Fessant, 19/08/2015 12:04 - > 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.
I don't think there is a clear need right now, but we may want one one day. An idea was to use plugins for specialising for different system (e.g. ocaml), but I don't think that's actually even needed (the most important need was for specific variables, and we are going towards defining them in the configuration, and from packages). > 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... That sounds dangerous ;) There is at the moment a check that specifically disables plugins named like a known command. The above could be quite straight-forward to implement, but I don't clearly see a use-case. _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
