Differences between revisions 9 and 10
Revision 9 as of 2013-08-28 11:08:27
Size: 6833
Editor: josch
Comment: added new label "test"
Revision 10 as of 2013-08-28 12:19:09
Size: 6885
Editor: josch
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
This document is currently a proposal for discussion, for which implementation patches exist. It is expected that an implementation in dpkg will be uploaded during the jessie cycle, enabling usage in the archive, at which point this will become policy documentation. This document is currently a proposal for discussion, for which implementation
patches exist. It is expected that an implementation in dpkg will be uploaded
during the jessie cycle, enabling usage in the archive, at which point this
will become policy documentation.
Line 7: Line 10:
For some compilation scenarios it is required to build-depend on a different set of binary packages than specified in the Build-Depends line. The two most important scenarios are: For some compilation scenarios it is required to build-depend on a different
set of binary packages than specified in the Build-Depends line. The two most
important scenarios are:
Line 12: Line 17:
This specification describes an extension of the Build-Depends field syntax. This extension allows the marking of build dependencies as being needed or not needed when a specific build profile is activated. It also defines a new field called "Build-Profile" which aids in marking binary packages as being built or not built whilst a certain build profile is activated or having been built with a certain set of build profiles activated. This specification describes two possible extensions of the Build-Depends field
syntax. These extensions allow the marking of build dependencies as being needed
or not needed when a specific build profile is activated. It also defines a new
field called "Build-Profile" which aids in marking binary packages as being
built or not built whilst a certain build profile is activated or having been
built with a certain set of build profiles activated.
Line 14: Line 24:
Build profiles can be activated by setting the environment variable DEB_BUILD_PROFILE or by using the -P option with dpkg-buildpackage (or -o Apt::Build-Profile for apt, or --profile in sbuild). More than one build profile can be activated at a time. Build profiles can be activated by setting the environment variable
DEB_BUILD_PROFILE or by using the -P option with dpkg-buildpackage (or -o
Apt::Build-Profile for apt, or --profile in sbuild). More than one build
profile can be activated at a time. Multiple profiles are specified by
separating them with commas. The initial profile names are "stage1", "stage2",
"test" and "cross".
Line 16: Line 31:
Binary packages which were built with one or more build profiles activated will have these profiles appended to their version number. Binary packages which were built with one or more build profiles activated will
have these profiles appended to their version number.
Line 26: Line 42:
This extends the architecture restriction syntax in square brackets from a single disjunctive list of architectures to a conjunctive list of logical disjunctions (a conjunctive normal form expression). Each clause of the conjunction is enclosed in square brackets. Every literal inside square brackets is a logical disjunction. The above example would therefore make the source package build depend on foo if the host architecture is either i386 or amd64 and if the build profile named "stage1" is not active. This extends the architecture restriction syntax in square brackets from a
single disjunctive list of architectures to a conjunctive list of logical
disjunctions (a conjunctive normal form expression). Each clause of the
conjunction is enclosed in square brackets. Every literal inside square
brackets is a logical disjunction. The above example would therefore make the
source package build depend on foo if the host architecture is either i386 or
amd64 and if the build profile named "stage1" is not active.
Line 34: Line 56:
The first group is called a namespace and the namespace "profile" is used to support build profiles. The second group is called a label and for the "profile" namespace the initial labels are "stage1", "stage2", "test" and "cross". The first group is called a namespace and the namespace "profile" is used to
support build profiles. The second group is called a label and specifies the
profile name.
Line 36: Line 60:
The other already existing namespace is "arch" for architectures. For backwards compatibility it is permitted to specify architecture labels without the "arch" namespace in front. The following are therefore equivalent: The other already existing namespace is "arch" for architectures. For backwards
compatibility it is permitted to specify architecture labels without the "arch"
namespace in front. The following are therefore equivalent:
Line 43: Line 69:
These literals can be negated by using an exclamation mark as a prefix. The literals inside a disjunction can be individually negated or not. To provide backwards compatibility, a disjunction which only contains architecture labels without the "arch" namespace must either be all negated or all positive. The following statements would therefore be legal: Literals can be negated by using an exclamation mark as a prefix. The literals
inside a disjunction can be individually negated or not. To provide backwards
compatibility, a disjunction which only contains architecture labels without
the "arch" namespace must either be all negated or all positive. The following
statements would therefore be legal:
Line 55: Line 85:
Literals of different namespaces cannot be mixed within a disjunction. Therefore, the following are be illegal: Literals of different namespaces cannot be mixed within a disjunction.
Therefore, the following are illegal:
Line 61: Line 92:
Should it ever be necessary, this restriction can easily be lifted at a later point. === Future extensions ===
Line 63: Line 94:
 * It could be allowed to allow different namespaces within a block
Line 74: Line 106:
This specification introduces a new pair of brackets (using < as the opening and > as the closing bracket) to be used after the architecture qualification list. Just as in the architecture qualification list, the literals within the <> brackets form a disjunction.
This specification introduces a new pair of brackets (using < as the opening
and > as the closing bracket) to be used after the architecture qualification
list. Just as in the architecture qualification list, the literals within the
<> brackets form a disjunction.
Line 83: Line 117:
The first group is called a namespace and the namespace "profile" is used to support build profiles. The second group is called a label and for the "profile" namespace the inital set of labels is "stage1", "stage2", "test" and "cross". The first group is called a namespace and the namespace "profile" is used to
support build profiles. The second group is called a label and specifies the
profile name.
Line 85: Line 121:
These literals can be negated by using an exclamation mark as a prefix. In contrast to the architecture qualification list, literals inside a disjunction can be individually negated or not. The following would be legal: These literals can be negated by using an exclamation mark as a prefix. In
contrast to the architecture qualification list, literals inside a disjunction
can be individually negated or not. The following would be legal:

Document status

This document is currently a proposal for discussion, for which implementation patches exist. It is expected that an implementation in dpkg will be uploaded during the jessie cycle, enabling usage in the archive, at which point this will become policy documentation.

Problem description

For some compilation scenarios it is required to build-depend on a different set of binary packages than specified in the Build-Depends line. The two most important scenarios are:

  • Bootstrapping (for breaking build dependency cycles) and
  • Cross building (for source packages having different build dependencies during cross building than during native building)

This specification describes two possible extensions of the Build-Depends field syntax. These extensions allow the marking of build dependencies as being needed or not needed when a specific build profile is activated. It also defines a new field called "Build-Profile" which aids in marking binary packages as being built or not built whilst a certain build profile is activated or having been built with a certain set of build profiles activated.

Build profiles can be activated by setting the environment variable DEB_BUILD_PROFILE or by using the -P option with dpkg-buildpackage (or -o Apt::Build-Profile for apt, or --profile in sbuild). More than one build profile can be activated at a time. Multiple profiles are specified by separating them with commas. The initial profile names are "stage1", "stage2", "test" and "cross".

Binary packages which were built with one or more build profiles activated will have these profiles appended to their version number.

Build-Depends syntax extension (option #1)

The syntax is as follows:

Build-Depends: foo (>= 1.0) [i386 arm] [!profile.stage1], bar

This extends the architecture restriction syntax in square brackets from a single disjunctive list of architectures to a conjunctive list of logical disjunctions (a conjunctive normal form expression). Each clause of the conjunction is enclosed in square brackets. Every literal inside square brackets is a logical disjunction. The above example would therefore make the source package build depend on foo if the host architecture is either i386 or amd64 and if the build profile named "stage1" is not active.

Every literal in a disjunction follows the following regular expression:

([a-z][a-z0-9-]*)\.([a-z][a-z0-9-]*)

The first group is called a namespace and the namespace "profile" is used to support build profiles. The second group is called a label and specifies the profile name.

The other already existing namespace is "arch" for architectures. For backwards compatibility it is permitted to specify architecture labels without the "arch" namespace in front. The following are therefore equivalent:

Build-Depends: foo [i386 arm64]
Build-Depends: foo [arch.i386 arch.arm64]

Literals can be negated by using an exclamation mark as a prefix. The literals inside a disjunction can be individually negated or not. To provide backwards compatibility, a disjunction which only contains architecture labels without the "arch" namespace must either be all negated or all positive. The following statements would therefore be legal:

Build-Depends: foo [profile.stage1 !profile.cross]

But the following would be illegal as it was before:

Build-Depends: foo [i386 !amd64]

Literals of different namespaces cannot be mixed within a disjunction. Therefore, the following are illegal:

Build-Depends foo [arch.i386 !profile.cross]

Future extensions

  • It could be allowed to allow different namespaces within a block

Build-Depends syntax extension (option #2)

An alternate syntax has been proposed and is also documented here.

The syntax is as follows:

Build-Depends: foo (>= 1.0) [i386 arm] <!profile.stage1 !profile.cross>, bar

This specification introduces a new pair of brackets (using < as the opening and > as the closing bracket) to be used after the architecture qualification list. Just as in the architecture qualification list, the literals within the <> brackets form a disjunction.

Every literal in a disjunction follows the following regular expression:

([a-z][a-z0-9-]*)\.([a-z][a-z0-9-]*)

The first group is called a namespace and the namespace "profile" is used to support build profiles. The second group is called a label and specifies the profile name.

These literals can be negated by using an exclamation mark as a prefix. In contrast to the architecture qualification list, literals inside a disjunction can be individually negated or not. The following would be legal:

Build-Depends: foo <profile.stage1 !profile.cross>

No other namespaces besides "profile" exist yet but it is forbidden to mix different namespaces within one disjunction.

Future extensions

  • The syntax could be extended to include multiple <> blocks as a conjunctive normal form expression, similar to the Build-Depends syntax extension option #1.

  • It could also be allowed to allow architecture names under the "arch" namespace within a <> block.

  • It could be allowed to allow different namespaces within a <> block

The Build-Profile field

The meaning of the Build-Profile field is similar (but orthogonal) to the Architecture field and also (just like the Architecture field) its meaning differs depending on where it is used.

debian/control binary package stanza

Here, the content of the Build-Profile field specifies the list of build profiles for which that binary package does or does not build. This list can either be all positive or all negative. Entries are negated by using an exclamation mark as a prefix.

Build-Profile: !cross !stage1

If a binary package stanza in a debian/control file does not contain a Build-Profile field, then it implicitly means that it builds with all build profiles.

*.changes and Packages file

Here, the content of the Build-Profile field specifies the list of build profiles for which that binary or source package was built for. It is also possible to identify binary packages which were built with one or more build profiles activated through their version number.

*.dsc file and Sources file

Just as the Architecture field in a Sources file, the Build-Profile field in a Sources file is automatically generated and specifies a list of build profiles which that source package supports. It is therefore the union of the build profile names given in the Build-Depends field and the build profile names given in the Build-Profile field in the binary package stanzas in the debian/control file.

Discussion