Johannes Rosenberger

Program code or config file? One could also simply allow verbatim xrandr options, like ```.yaml configure_row: - LVDS1: "--scale 1.2x1.2" - VGA1@1920x1080 ``` Alternatively, one could give an argument list,...

Why not declare profiles nixos options in a module like this ~~~nix { lib, ... }: let profile = with lib; mkOptionType { name = "profile"; description = "module not...

I tested it with [this nix expression](https://paste.sr.ht/~jorsn/a7343123a99f1e081cf74ece0e6f128edd82e3d4) (using method (1) and dune directly), and with opam installation into $HOME/.opam/default and autodetection (method (2)). I checked if the path is correct...

I forgot to add the configure script… now it's there.

Converted to draft to wait for answers in ocaml/dune#1185, since ocaml/dune#3104 probably made this a bit more consistent, maybe even far easier (see [ocaml/dune#1185 (comment)](https://github.com/ocaml/dune/issues/1185#issuecomment-691928991_)).

in fact, at least some source files refer to GPL v3+ This should be clarified. Are you planning to do this?

Maybe it would be good to extract the prefix directory from the build at compile time instead of relying on runtime `opam var share` or hardcoding `/usr/local/` in `unicodelib/config.ml` and...

Yes, it seems one cannot detect it reliably, only in some cases (see [my comment in ocaml/dune#1185](https://github.com/ocaml/dune/issues/1185#issuecomment-691508200_)). One could use `opam config var prefix` (you require opam anyway) in a...

If I understand correctly, this now allows for completely arbitrary paths, doesn't it? This is the current behavior of real flakes. As flake-compat should mimic real flake behavior, note [this...

Well, currently flake-compat is more strict than real flakes by not allowing relative paths. I don't think it is clear wether "path:../" will be allowed in the future, but relative...