po4a-Bugs item #315040, was opened at 2015-04-06 14:57 by John Hein You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=31... Status: Open Priority: 3 Submitted By: John Hein (gettowork-guest) Assigned to: Nobody (None) Summary: [patch] fix path to man pages when '--install_path man' is specified Category: None Group: None Resolution: None Initial Comment: If you call Build.PL with --install_path bindoc=/some/different/path, that path will not be where man pages go when you run 'Build install'. Instead it uses the man page installation directory from the default perl configuration. '--install_path lib' and '--install_path bin' work as expected. But the bindoc specification is used in Po4aBuilder.pm's ACTION_install to override Module::Build's normal handling for some man pages. However, the man pages do not go to the install_path for bindoc specified by the command line --install_path option. The attached patch attempts to fix the situation by using the 'install_path' set of directories when processing the mandir location. To repeat the observed problem, try configuring by using something like the following: perl Build.PL --destdir=/tmp --install_path lib=/some_nonexistent_temp_dir/lib/perl/site_perl --install_path bin=/some_nonexistent_temp_dir/bin --install_path script=/some_nonexistent_temp_dir/bin --install_path bindoc=/some_nonexistent_temp_dir/man/man1 --install_path libdoc=/some_nonexistent_temp_dir/lib/perl/site_perl/man/man3 --install_path man=/some_nonexistent_temp_dir/lib/perl/site_perl/man Then install using: perl Build --destdir=/tmp Notice that some of the man pages are not installed under /tmp/some_nonexistent_temp_dir ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410622&aid=31...