Bug 110958
| Summary: | interactive configuration macros for rpm spec file | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Kaplan <dmkaplan> |
| Component: | rpm | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | athlon | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-11-30 15:03:15 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: | |||
Ick. No way, rpm is intended for unattended batch builds. Putting a timer on input will not solve all possible cases, there will always be someone who complains that rpm is broke because timer has not expired while someone else is complaining that timer is expirong too fast. Edit the spec file, do what you want with a text editor, instead. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: How hard would it be to provide a set of macros to make it easier to develop interactive configuration routines in the %post, %pre, etc. sections of rpm installs? I am thinking of a set of macros that test if rpm is being run interactively and if a GUI is available. There could also be timed tests to see if the user wants to deal at that moment (like Kudzu). This would address one of the key issues that people are always complaining about regarding RPMs. Version-Release number of selected component (if applicable): rpm-4.2-0.69 How reproducible: Always Steps to Reproduce: 1.blah, blah 2. 3. Additional info: