Bug 143571
Summary: | RFE: Add resolving of dependencies via yum / integrate with up2date | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Anderson <david> |
Component: | system-config-packages | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | mattdm |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-21 19:54:19 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
David Anderson
2004-12-22 15:07:44 UTC
An additional complication occurs when the RPM you grab has non-standard dependencies. In many cases the site you got the RPM from includes packages of the dependencies. (For example, grabbing a Gossip RPM probably needs a Loudmouth RPM, which needs GNU-TLS and so on.) If a RPM could include an additional header/key specifying the site/vendor it came from and a repository for that site then the installer could temporarily add that repository during dependency resolution. This would allow a vendor to put an RPM on their site and a private repository of dependencies, and the user can just click Install Package (a link to the main RPM) and have it and its dependencies installed. Any temporary repositories should probably default to requiring GPG key signing and verifying and require that all packages from the repository be signed by the same key as the package that linked to the repository. Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. This RFE seems pretty well-phrased. Moving from FC2 to devel. The next generation tool will handle this much better |