Ocaml-devel June 2022

ocaml-devel@lists.fedoraproject.org

6 participants
5 discussions

ocaml dune 3
by Richard W.M. Jones 05 Jul '22

05 Jul '22

Annoyingly now that I've done the OCaml rebuild, I discovered that the version of Dune that we're shipping is quite old. Fedora Rawhide ships 2.9.3, latest upstream is 3.3.1. https://bugzilla.redhat.com/show_bug.cgi?id=2002676 This wouldn't necessarily matter, but I found a new package that depends on 3.x: https://bugzilla.redhat.com/show_bug.cgi?id=2099754 Well, it _may_ work with 2.9 (after hacking the dune-project file) but it fails a bit later because of some missing dependencies so I'm not entirely sure. Anyhow, I wonder if there's a reason why we're sticking with dune 2.9, or if I can upgrade it? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html

3 5

odoc
by Jerry James 30 Jun '22

30 Jun '22

Back when I started working on packaging the dependencies of odoc, I had a vision of a tree of nicely cross-referenced documentation for Fedora OCaml packages. That vision has not come to pass, and probably never will. To achieve it, we would have to do bootstrap builds of all packages in the odoc dependency tree, then start the builds over again with documentation included. That would be a big hassle. Most of the documentation is online anyway, and OCaml developers will probably use opam to generate a tree of nicely cross-linked documentation, so the payoff for doing that extra work would be small. As a result, I propose that going forward we remove odoc from the BuildRequires of OCaml packages and consequently stop building the documentation. Does anybody object? -- Jerry James http://www.jamezone.org/

3 3

Re: Package proposal: google-drive-ocamlfuse
by Dan Čermák 30 Jun '22

30 Jun '22

Marián Konček <mkoncek(a)redhat.com> writes: > I recently discovered this project: > https://github.com/astrada/google-drive-ocamlfuse > > Supposedly it makes it possible to mount google drive as a filesystem > using fuse. > > I wanted to try to package it myself, but ocaml seems a bit esoteric and > we are currently missing at least 5 dependencies in Fedora. > > Nevertheless I think this package would be useful for many people. > > Would anyone (perhaps someone who maintains other ocaml packages) be > willing to package this? The problem with this is, that the most active OCaml packagers are Rich Jones and Jerry James, who already have a ton of packages on their plate. Unless they have a specific use for this tool, I wouldn't shove it on theirs (unless they want of course ;-) ). I have a different proposal though: I have a little bit of experience with OCaml packaging and some time this week, so if you want, I can try to guide you through OCaml packaging. Cheers, Dan

3 2

OCaml spec file support macros
by Jerry James 30 Jun '22

30 Jun '22

Hi all, I've been experimenting with adding some macros to make OCaml packaging a bit easier. You can see what I have so far here: https://src.fedoraproject.org/fork/jjames/rpms/ocaml-srpm-macros/c/9554c809… With these macros, the main part of a spec file for a package that builds with dune can be as simple as this: ``` %build %dune_build %install %dune_install %check %dune_check %files -f .ofiles %doc README.md %license LICENSE.md %files devel -f .ofiles-devel ``` Packages that do not use dune to build can still use the %ocaml_files macro at the end of %install to generate .ofiles and .ofiles-devel files to pass to %files. New macros: - %ocamldir: shorter replacement for %{_libdir}/ocaml - %odoc_package: inspired by %javadoc_package, everything you need in one place to declare a package that contains odoc documentation. - %relink_stublibs: automatically locate any dll*.so files created by ocamlmklib and relink them with Fedora linker flags - %_add_release_func: internal macro to add `--release` to flags passed to %dune_build or %dune_check if neither `--release` nor `-p` has been given. I should probably rewrite it in lua. - %dune_build: invoke `dune build` with a standard set of flags, followed by %relink_stublibs. Arguments can be passed to dune, e.g., `%dune_build @install`. - %dune_check: invoke `dune runtest` with a standard set of flags. Arguments can be passed to dune, e.g., `%dune_check -p foobar`. - %ocaml_files: generate .ofiles* files to pass to %files from files installed in the buildroot. Use of this macro requires python3 to be installed in the chroot. By default, files are split into a main package (.ofiles) and a devel package (.ofiles-devel). Use `%ocaml_files -n` to ump all files together into .ofiles. Use `%ocaml_files -s` to generate files with the OCaml module name embedded in them; e.g., .ofiles-module1, .ofiles-module1-devel, .ofiles-module2, .ofiles-module2-devel, etc. - %dune_install: invoke `dune install` with a standard set of flags, then: - Remove any .dune-keep markers left over from running odoc - Remove anything installed into /usr/doc - Remove all *.ml files that have matching *.mli files installed - Invoke %ocaml_files, with the same -s or -n options passed to %dune_install itself I would appreciate any feedback you can offer. My questions: 1. Is ocaml-srpm-macros the best place for this? 2. Is the python dependency for %ocaml_files / %dune_install okay? I thought about writing it in lua to avoid the external dependency, but then the entire %install script has to be written in lua. If the entire %install script is just %dune_install, then that's okay, but it seems like a significant barrier otherwise. 3. Can you think of any other macros that would be useful? 4. I wonder if it would be useful to allow overrides for the logic used by %ocaml_files to split files into the main and devel packages. Perhaps something like this: -d file1,file2,...: comma-separated list of files to put in the devel package, even if they would normally go in the main package -m file1,file2,...: comma-separated list of files to put in the main package, even if they would normally go in the devel package Too bad for you if you want to do this to a file with a comma in its name. :-) Of course, one can always do surgery on the .ofiles* files after they are created, so maybe this would be overkill. I was working on making a bunch of spec files for everyone to look at when the package notes feature derailed me. Sigh. I'm going to get that cleaned up first, then I hope to get back to making examples. Regards, -- Jerry James http://www.jamezone.org/

4 9

OCaml 4.14
by Richard W.M. Jones 22 Jun '22

22 Jun '22

Been a bit busy of late (writing OCaml code though ..), but as you can see there's a new OCaml compiler out, 4.14.0: https://ocaml.org/releases/4.14.0.html I intend to update to this in the next few days, only in Rawhide. But before that are there any other OCaml packages that you think should be updated first? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW

2 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Ocaml-devel June 2022