Bug 78608
| Summary: | [RFE] up2date should allow users to download packages by specifying a file name | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Michael Lee Yohe <michael> |
| Component: | up2date | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED WORKSFORME | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | gafton, mihai.ibanescu |
| 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: | 2003-08-06 22:55:47 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
Michael Lee Yohe
2002-11-26 13:57:53 UTC
Have you tried: up2date --whatprovides /usr/bin/joe This will show you the name, version and release of the package providing that file. You can then up2date that package. Would this work for you? I'm familiar with the --whatprovides option. However, I think either adding the ability to say: # up2date --whatprovides /usr/bin/jed jed-0.99.15-3 No additional dependencies are necessary to install this package. Continue with installation (Y/n) : __ OR __ Something that up2date does not currently allow: # up2date --whatprovides stty sh-utils-2.0.12-3 No additional dependencies are necessary to install this package. Continue with installation (Y/n) : Currently, it does not report anything (since I did not resolve the path). Some users will not understand that some things are placed in /usr/bin, /usr/sbin, /bin, /sbin. If, for some reason, a file name is located in two different spots (and owned by two different packages) - the ambiguity is reported to the user and tells them the name of the packages that contain that file name. The aforementioned abilities should be provided in the graphical client since most users will use the Gnome frontend to up2date. See Bug 78610. It would be easy for the user to determine which package to select, eliminating the ambiguity, by allowing them to read the package description. I just thought of another reason this is kind of important. "Gnome Pilot" is packaged in "gnome-pilot", but most of the executable files are all named starting with gpilot or gpilotd. Having RHN search its database for all packages containing "gpilotd" within an architecture would simplify package installation. up2date --solvedeps /usr/bin/jed will find what solves the dep, and all it's deps, and install it. Theres no gui component of this as yet, though I currently working on something along that line. |