summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorVincent Laporte <Vincent.Laporte@gmail.com>2022-01-19 11:16:45 +0100
committerVincent Laporte <vbgl@users.noreply.github.com>2022-01-26 07:35:19 +0100
commitcea532f629a7004e622bf0f334b3f8f8e1a0f06f (patch)
tree93f44df76684fc630be3d3e42ffe8b0d358fe7b2 /doc
parent4d922730369d1c468cc4ef5b2fc30fd4200530e0 (diff)
downloadnixpkgs-cea532f629a7004e622bf0f334b3f8f8e1a0f06f.tar
nixpkgs-cea532f629a7004e622bf0f334b3f8f8e1a0f06f.tar.gz
nixpkgs-cea532f629a7004e622bf0f334b3f8f8e1a0f06f.tar.bz2
nixpkgs-cea532f629a7004e622bf0f334b3f8f8e1a0f06f.tar.lz
nixpkgs-cea532f629a7004e622bf0f334b3f8f8e1a0f06f.tar.xz
nixpkgs-cea532f629a7004e622bf0f334b3f8f8e1a0f06f.tar.zst
nixpkgs-cea532f629a7004e622bf0f334b3f8f8e1a0f06f.zip
manual: document deprecated `minimumOCamlVersion`
Diffstat (limited to 'doc')
-rw-r--r--doc/languages-frameworks/ocaml.section.md14
1 files changed, 11 insertions, 3 deletions
diff --git a/doc/languages-frameworks/ocaml.section.md b/doc/languages-frameworks/ocaml.section.md
index d266a032268..47035551d41 100644
--- a/doc/languages-frameworks/ocaml.section.md
+++ b/doc/languages-frameworks/ocaml.section.md
@@ -32,9 +32,9 @@ Given that most of the OCaml ecosystem is now built with dune, nixpkgs includes
 
 Here is a simple package example.
 
-- It defines an (optional) attribute `minimalOCamlVersion` that will be used to
-  throw a descriptive evaluation error if building with an older OCaml is
-  attempted.
+- It defines an (optional) attribute `minimalOCamlVersion` (see note below)
+  that will be used to throw a descriptive evaluation error if building with
+  an older OCaml is attempted.
 
 - It uses the `fetchFromGitHub` fetcher to get its source.
 
@@ -117,3 +117,11 @@ buildDunePackage rec {
   };
 }
 ```
+
+Note about `minimalOCamlVersion`.  A deprecated version of this argument was
+spelled `minimumOCamlVersion`; setting the old attribute wrongly modifies the
+derivation hash and is therefore inappropriate. As a technical dept, currently
+packaged libraries may still use the old spelling: maintainers are invited to
+fix this when updating packages. Massive renaming is strongly discouraged as it
+would be challenging to review, difficult to test, and will cause unnecessary
+rebuild.