Bug 57326 - `macro-ization' of spec files generated by cpanflute
Summary: `macro-ization' of spec files generated by cpanflute
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm-build (Show other bugs)
(Show other bugs)
Version: 7.2
Hardware: All Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2001-12-10 14:40 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-29 21:45:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
`macro-ization' of spec files generated by cpanflute (4.10 KB, text/plain)
2001-12-10 14:50 UTC, Need Real Name
no flags Details

Description Need Real Name 2001-12-10 14:40:26 UTC
When creating (s)rpm's from perl modules I use a slightly
modified version of the cpanflute script found in the
rpm-build-4.0.3-1.03 package.

The purpose of the `macro-ization' of the generated spec file 
is to minimize the changes people need to make to the spec file
when they update a package in between redhat releases.

Please do a diff with /usr/lib/rpm/cpanflute and change what you like.

Comment 1 Need Real Name 2001-12-10 14:50:12 UTC
Created attachment 40267 [details]
`macro-ization' of spec files generated by cpanflute

Comment 2 Jeff Johnson 2002-02-24 17:28:27 UTC
rpm-4.0.4 contains a cpanflute2 script that
will be used in the future. In addition,
this script will end up in a CPAN package,
not in rpm-build in the future, so I'm gonna
assign to the guy who wrote cpanflute2.

Comment 3 Bill Nottingham 2005-09-29 21:45:31 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of

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.