Bug 52649 - h2ph is not part of the standard perl installation
Summary: h2ph is not part of the standard perl installation
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: perl (Show other bugs)
(Show other bugs)
Version: 9
Hardware: All Linux
medium
low
Target Milestone: ---
Assignee: Chip Turner
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-27 17:49 UTC by Nick Simicich
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-04-11 21:15:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nick Simicich 2001-08-27 17:49:28 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
Lots of scripts want to look at .ph files. A specific reason for this 
would be to get exit codes for mail processor exits out of sysexits.ph.  
Redhat's default perl installation foes not run h2ph and it should.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install a system.
2. Note that the .ph files are missing
3.
	

Actual Results:  File not found.

Expected Results:  The perl include should have worked.

Additional info:

See the h2ph man page for instructions on running h2ph.  This is something 
that any administrator *can* do, but it is really part of installing 
perl.  If the perl RPM does not do this, it is only doing a partial 
install.
Comment 1 Chip Turner 2003-04-11 21:15:59 UTC 
.ph files are generated for some headers at build time but not runtime.  .ph
files are included as a convenience for compatibility but are largely depracated
for regular usage.
Note You need to log in before you can comment on or make changes to this bug.