m (Removed {{Draft}}) |
m (Fixed up grammar.) |
||
| Line 13: | Line 13: | ||
== Architecture Support == | == Architecture Support == | ||
'''All Fedora packages must successfully compile and build into binary rpms on at least one supported primary architecture, | '''All Fedora packages must successfully compile and build into binary rpms on at least one supported primary architecture, except where the package is useful only on a secondary architecture (such as an architecture-specific boot utility, microcode loader, or hardware configuration tool).''' Fedora packagers should make every effort to support all primary architectures. | ||
Content, code which does not need to compile or build, and architecture independent code (noarch) are notable exceptions. | Content, code which does not need to compile or build, and architecture independent code (noarch) are notable exceptions. | ||
Latest revision as of 18:03, 13 October 2011
Existing Guideline
Architecture Support
All Fedora packages must successfully compile and build into binary rpms on at least one supported primary architecture. Fedora packagers should make every effort to support all primary architectures.
Content, code which does not need to compile or build, and architecture independent code (noarch) are notable exceptions.
Proposal
Architecture Support
All Fedora packages must successfully compile and build into binary rpms on at least one supported primary architecture, except where the package is useful only on a secondary architecture (such as an architecture-specific boot utility, microcode loader, or hardware configuration tool). Fedora packagers should make every effort to support all primary architectures.
Content, code which does not need to compile or build, and architecture independent code (noarch) are notable exceptions.
Discussion
See Talk:PackagingDrafts/MustBuildOnPrimaryArchitecture for rationale and discussion.