Clarify that [[package.build-requires]] is locked

python · brettcannon · Jul 24, 2024 · Mar 20, 2024 · Mar 21, 2024 · Mar 21, 2024
commit 0c45e8771301f4fe8da90cdeda6c5db9b105fa1d
@@ -216,6 +216,7 @@ other is disallowed.
   considered compatible for the same environment.
 - In instances where there would be a conflict but the lock is still desired,
   either separate lock files can be written or per-package locking can be used.
+- Entries in array SHOULD be sorted by ``file-lock.name`` lexicographically.
 
 
 ``file-lock.name``
@@ -406,6 +407,8 @@ other is disallowed.
 - Array of tables
 - Tables can be written inline.
 - Represents the files to potentially install for the package and version.
+- Entries in ``[[package.files]]`` SHOULD be lexicographically sorted by
+  ``package.files.name`` key to minimze changes in diffs.
 
 
 ``package.files.name``
@@ -414,8 +417,6 @@ other is disallowed.
 - String
 - The file name.
 - Necessary for installers to decide what to install when using package locking.
-- Entries in ``[[package.files]]`` SHOULD be lexicographically sorted by this
-  key to minimze changes in diffs.
 
 
 ``package.files.lock``
@@ -527,6 +528,9 @@ other is disallowed.
 - An array of tables whose structure matches that of ``[[package]]``.
 - Each entry represents a package and version to use when building the
   enclosing package and version.
+- The array is complete/locked like ``[[package]]`` itself (i.e. installers
+  follow the same installation procedure for ``[[package.build-requires]]`` as
+  ``[[package]]``)
 - Selection of which entries to use for an environment as the same as
   ``[[package]]`` itself, albeit only applying when installing the build
   back-end and its dependencies.