Indeed, to be honest, these are terms we use internally and the name of fields in the opam package format, but we should otherwise be explicit -- for the field names it's documented, but otherwise users aren't supposed to know about them.
On [1], the term appears as the name of a field under the "Optional dependecies" title so that seems clear enough ? Cheers, Louis [1] https://opam.ocaml.org/doc/Packaging.html Le lundi 24 novembre 2014, 13:33:41 Amir Chaudhry a écrit : > Hi folks, > > Apologies if this naive but I wonder if the terms we use to describe > dependencies are widely used. I ask because I've only learned the meanings > by osmosis and some quick google searching doesn't lead me to any neat > explanations. Had I come across these for the first time by myself, I'd > likely be confused (I didn't find them self-explanatory in the beginning). > > * Dep(s) -- Dependencies > * depopt(s) -- Optional dependency > * depext(s) -- External dependency > > Am I missing any? I wondered about writing a short blog post or glossary so > that these terms might surface somewhere more easily [1] (I do note that > 'depopt' appears once in the packaging instructions [2]). > > I thought I'd post this here just in case it provokes some thoughts. > > Best wishes, > Amir > > [1] Something similar to > http://mirror.ocamlcore.org/ocaml-tutorial.org/glossary.html > [2] https://opam.ocaml.org/doc/Packaging.html > > _______________________________________________ > opam-devel mailing list > [email protected] > http://lists.ocaml.org/listinfo/opam-devel _______________________________________________ opam-devel mailing list [email protected] http://lists.ocaml.org/listinfo/opam-devel
