Bug 56005 - RFE: provide specfile(5) documentation
Summary: RFE: provide specfile(5) documentation
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm-build
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-10 11:44 UTC by Edward J. Huff
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-09-29 21:48:31 UTC
Embargoed:


Attachments (Terms of Use)
Fix problem in man page -- where do spec files come from? (1.50 KB, patch)
2001-11-10 11:48 UTC, Edward J. Huff
no flags Details | Diff

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.


Note You need to log in before you can comment on or make changes to this bug.