From 8409aa86409e0ea2673313c91506f6cc73a733fa Mon Sep 17 00:00:00 2001 From: Patrick McDermott Date: Wed, 17 Jun 2020 16:18:24 -0400 Subject: SPF 2.0: More section restrictions and rationale --- (limited to 'specs') 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. -- cgit v0.9.1