Bug 22328 - perl-5.6.0 will not rebuild on RHL62 due to fhs patch
perl-5.6.0 will not rebuild on RHL62 due to fhs patch
Product: Red Hat Raw Hide
Classification: Retired
Component: perl (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Chip Turner
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2000-12-15 01:04 EST by Pekka Savola
Modified: 2005-10-31 17:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-11 16:34:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pekka Savola 2000-12-15 01:04:55 EST
perl-5.6.0-11 will not rebuild on RHL6x due to fhs patch forcing
the man page installation to /usr/share/man but %{_mandir} macro
in the spec file trying to find them from /usr/man.

%{_mandir} should probably be changed to /usr/share/man because
it won't work with any other options anyway..
Comment 1 kenneth_porter 2000-12-21 05:16:40 EST
The problem is the FHS patch, which hard-codes the mandir in hints/linux.sh and lib/ExtUtils/MM_Unix.pm. I created an alternative spec file that disables 
the patch and passes the mandir macro to Configure. This handles the hints file, but not the MM_Unix.pm module. That file may need to be patched 
dynamically from some script in the spec file.
Comment 2 kenneth_porter 2000-12-21 05:25:23 EST
I'd attach the revised spec file but I don't see that option for this bug entry in Bugzilla. Here's a context diff:

< Release: 11
> Release: 12
< %patch6 -p1 -b .fhs
> # patch to hints/linux.sh replaced with Configure option,
> # still need equivalent for lib/ExtUtils/MM_Unix.pm though...
> # %patch6 -p1 -b .fhs
> 	-Dman1dir=%{_mandir}/man1 \
> 	-Dman3dir=%{_mandir}/man3 \
> * Thu Dec 21 2000 Kenneth Porter <shiva@well.com>
> - Pass RPM mandir to Configure for pre-FHS systems

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