SPF 2.0: More section restrictions and rationale

1 files changed, 9 insertions, 5 deletions

diff --git a/specs/spf-2.0/fields.mdwn b/specs/spf-2.0/fields.mdwn
index 11cfbe8..85a9ec4 100644
--- a/specs/spf-2.0/fields.mdwn
+++ b/specs/spf-2.0/fields.mdwn
@@ -87,11 +87,15 @@ The fields in the binary package metadata are:
       utilities and binaries run by other programs.
 
     No packages may declare any relationships (via `Depends`, `Recommends`,
-    etc.) with packages in sections `dbg`, `doc`, or `locale`.  Only binary
-    packages in section `dev` and source packages (via `Build-Depends`) may
-    declare relationships with packages in section `libdev`.  These restrictions
-    allow feed lists for sections `dbg`, `doc`, `libdev`, and `locale` to be
-    excluded from systems that don't need the packages they contain.
+    etc.) with packages in sections `dbg`, `doc`, or `locale`.  Only packages
+    in section `boot` may declare relationships on other packages in the same
+    section.  Only binary packages in section `dev` and source packages (via
+    `Build-Depends`) may declare relationships with packages in sections `dev`
+    and `libdev`.  These restrictions allow feed lists for sections `boot`,
+    `dbg`, `dev`, `doc`, `libdev`, and `locale` to be excluded from systems that
+    don't need the packages they contain.  That is, only sections `lib`,
+    `share`, and `utils` are available on all systems, and additionally sections
+    `dev` and `libdev` are available when building packages.
 
     All packages in sections `lib` and `libdev` must allow coinstallation of
     packages of the same name and different architectures.