Bug 110875
| Summary: | RFE: Multi-host functionality for RPM | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Need Real Name <sysadmin> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | 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-01-26 10:18:24 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: | |||
Up2date has much of this functionality already. Otherwise, this is more of a dependency solver than rpm issue. FOr example, there is no reason why yum could not be taught to access databases on multiple hosts. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030708 Description of problem: I'd like RPM to be able to support multiple hosts. I would suggest as an initial step that RPM be set to use a central database. Naturally I would suggest PostgreSQL, but I don't particularly mind which FOSS database is chosen. Long-term, I personally would like to be able to have something like yum or apt-rpm update multiple hosts based on cfengine configuration (and downloading from a central repository in my network to save bandwidth), but obviously none of that can happen without a centralised database of RPMs. If RPM itself were to do this, that would be the optimal solution. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Google "rpm database backend" 2. Google "rpm multi-host package manager" 3. Observe that neither of these produce any hits which appear to supply the requested functionality 4. Sorry about this, the form won't let me submit without it 5. ??? 6. Profit!!! Additional info: