Bug 133778
Summary: | libgcc predepends on something it provides itself | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Dag Wieers <dag> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 00:14:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dag Wieers
2004-09-27 12:39:33 UTC
That is an apt bug then. This dependency is not explicitely in gcc (or glibc) spec file, rpm adds it automatically when it sees a scriptlet. Yes, apt-rpm bug. rpm does not distinguish between PreReq: and Requires:, the two are synonyms, treated exactly the same. This is rpm behavior since RHL 6.2. FWIW, Gustavo sez' that the apt-rpm in use here is deviant from what he uses. You might want to check what apt-rpm you are using. Ok, I verified this and contrary to what I believed it indeed was a very dated: apt-0.5.4cnc9-1.dag.rh73.i386.rpm Sorry for that and thanks for the prompt replies. Still I'm wondering if it would make sense to change RPM so it wouldn't add these requirements if the package itself provides it and eg. it is required by a %post or %preun script. It would probably save some diskspace, bandwidth, memory and CPU cycles if both RPM and apt/yum does not have to handle that. Maybe something that can quickly be checked what the overhead is. A quick biased example, the perl package has 194 dependencies, of which 188 point to its own package ! I reopened this bug and changed severity to 'enhancement' in order to re-evaluate the changed focus of this bug. In case a new bugreport is required or you just want me to shut up, please close again :) (digest from irc discussion) While it may seem to make no sense from a package POV that /usr/bin/perl has Provides: perl <= 3:5.8.5 while the horde of included *.pl modules have myriad Requires: perl >= 0: 5 and many more, the rationale for not automagically reducing the package dependencies by checking for overlapping ranges and choosing the broadest range is that, in fact, the Provides: and Requires: are attached to different objects within the package, the Provides: from /usr/bin/perl (and other elements), while the Requires: are as specified (and automagically extracted) in various *.pl scripts within. The elements are different, and rpm can do no more than carry the dependencies as specified by the packager. |