Bug 56005

Summary: RFE: provide specfile(5) documentation
Product: [Retired] Red Hat Linux Reporter: Edward J. Huff <ejhuff>
Component: rpm-buildAssignee: Jeff Johnson <jbj>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: stephen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-29 21:48:31 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:
Attachments:
Description Flags
Fix problem in man page -- where do spec files come from? none

Description Edward J. Huff 2001-11-10 11:44:49 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-7 i586)

Description of problem:
The man page should explain how to obtain the spec file
in order to unpack the sources without recompiling and 
installing the package.  Also 'rathen' should be 'rather'.

Version-Release number of selected component (if applicable):
rpm-4.0.3-1.03.src.rpm

How reproducible:
Always

Steps to Reproduce:
1. man rpm
2. /rathen
3. /spec *file
	

Additional info:

patchfile attached.
Comment 1 Edward J. Huff 2001-11-10 11:48:28 UTC 
Created attachment 37181 [details]
Fix problem in man page -- where do spec files come from?
Comment 2 Jeff Johnson 2001-11-20 16:28:32 UTC 
Thanks for the patch. However, since rpm build modes
are now resident in /usr/bin/rpmbuild, and documented
in rpmbuild(8), the patch should go there.

Furthermore, and more importantly, spec files really need
to be documented in specfile(5). So I'm gonna change this
into a RFE for specfile(5).
Comment 3 Bill Nottingham 2005-09-29 21:48:31 UTC 
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

For RPM issues, please try a current release such as Fedora Core 4; if bugs
persist, please open a new issue.