Summary: | RPM needs an Architecture: tag | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthias Urlichs <smurf> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-09-14 18:08:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: |
Description
Matthias Urlichs
1999-10-28 00:58:48 UTC
This feature comes up from time to time on rpm-list. Here's the current rationale for not providing the feature: The lack of the ability to have a noarch sub-package is a conscious design decision in rpm. The intent has been that the arch/os platform is unchanged throughout the processing of a spec file on a build system in order to provide a stronger guarantee that the binary packages are associated with a single source package generated on a single build host at a certain moment in time. Permitting a sub-package with "BuildArch: noarch" weakens this guarantee because there would be a set of generated noarch packages, one from each of the build platforms, all with the same name, some of which may not "work" (consider packaging something like X11 fonts in a noarch package that might have byte-order dependencies in older formats) dependent on which build host was used to produce the noarch package. Gonna close this, as I can't change the behavior. |