05:53 <discocaml> <loreleioo> Cuz you said until it isn't

09:43 <pgiarrusso> I understand OCaml is still supported and used a lot at INRIA, which is a French state organization for applied research? For instance https://www.inria.fr/en/cambium-ocaml-programming-language-software, but I don't know INRIA's rank among contributors

09:47 <discocaml> <Kali> > OCaml is a free and open-source software project managed and principally maintained by the French Institute for Research in Computer Science and Automation (Inria).

09:47 <discocaml> <Kali> https://en.wikipedia.org/wiki/OCaml

11:33 <octachron> Note that it is more than there are researchers at INRIA that work on OCaml on their academic free time. INRIA direct support amounts to 1 research engineer working full time on OCaml.

14:27 <hiddenman> hi all. could anyone help with a simple thing: i'm building an ocaml package under Debian in the isolated chroot. i did install ocaml + few debian ocaml libraries, for example, xml-light. then i did opam init; "opam pin pkg git-url" for some local packages and then tried to build. however, i always get an error "Error: Library "xml-light" not found" while it exists at the /usr/lib/ocaml/xml-light

14:28 <hiddenman> tried to play with different CAML_LD_LIBRARY_PATH but that didn't help.

14:29 <hiddenman> what variable is used for searching libraries? default Debian installation must be able to find everything, but it didn't

14:30 <zozozo> hiddenman: by default, opam installs (and performs lookups for) ocaml packages in its own directories, typically something such as `~/.opam/<switch_name>`

14:30 <zozozo> I'm not sure opam intends to support mixed situations where some packages are installed by the system, and others are installed via opam

14:31 <hiddenman> zozozo, yes, i even tried to did opam switch create 4.13.1

14:31 <zozozo> hiddenman: I'd say the solution is to install cml-light via opam rather than via the debian package

14:31 <zozozo> *xml

14:32 <hiddenman> zozozo, then i will have to install _all_ required libraries which are supplied by Debian by default? bad news then

14:33 <hiddenman> so no mix of system and local packages. thought the same but hoped it would not happen :)

14:34 <zozozo> hiddenman: I might be wrong, but I never tried it, and from what you're saying, it doesn't seem to work, but I'll ask some people to confirm

14:35 <hiddenman> zozozo, i will try and let you know as well. i thought there is envvar like CAML_LD_LIBRARY_PATH which is used to search for libraries

14:57 <hiddenman> zozozo, adding xml-light as "opam pin xml-light local_git_url" helped. now it wants all other libraries to compile. it's weird it can mix system and local

21:25 <discocaml> <barconstruction> I just stumbled across a piece of really ham fisted anti-woke political satire that Xavier Leroy posted on his professional website and i wish this had been covered in real world ocaml (two short paragraphs introducing him and explaining that he is a boomer) rather than me getting blindsided by it.

21:26 <discocaml> <barconstruction> he probably got it sent to him in a chain email twenty years ago and was like "Ha! So true!" and posted it on his website and forgot about it

21:57 <waleee> if it isn't something extremly inappropriate or offensive I don't really see the point

22:17 <waleee> @barconstruction I presume it was something on this subpage? https://xavierleroy.org/stuff/

22:18 <discocaml> <barconstruction> yes haha

22:19 <discocaml> <barconstruction> also i wasn't serious i was just expressing surprise in a hyperbolic way

22:20 <waleee> yeah, I was trying to see how why you was riled up over a page he himself has marked as "my geek humor page that is getting a bit old"

23:34 <discocaml> <barconstruction> Oh, I found it via google so I didn't see the label.

23:52 <src> I'm a bit confused then to explicitly define a module via `module MyModule = struct ... end` and when not to when relying on dune since a module of name MyModule is implicitly created anyways by the build system?

23:52 <src> so I'd have `MyModule.MyModule.myfunction` instead of `MyModule.myfunction`

23:52 <src> s/then/when

23:54 <src> questions I guess are a) is there simply no use case for explicit module declaration when using dune? b) is there a legitimate way to do explicit module declaration when using dune without adding the layer of indirection I talked about