Changes between Version 2 and Version 3 of Ticket #46057, comment 8
- Timestamp:
- Dec 30, 2014, 6:46:08 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #46057, comment 8
v2 v3 3 3 The more traditional way to resolve the conflicts is to fix the port to install any binaries in ${perl5.bindir}. This variable's default is set by the perl5 portgroup to the versioned directory ${prefix}/libexec/perl${perl5.major}. When binaries exist in this directory, the portgroup automatically creates versioned symbolic links to them in ${prefix}/bin resolving possible conflicts. 4 4 5 In addition, there are some miscellaneous issues with the port's Makefile that can be handled more simply by patching the Makefile directly. These include the creation of required installation directories in ${destroot} and enabling the installation of html documentation which is 6 currently comment out in the distributed Makefile. 5 In addition, there are some miscellaneous issues with the port's Makefile that can be handled more simply by patching the Makefile directly. These include the creation of required installation directories in ${destroot} and enabling the installation of html documentation which is currently commented out in the distributed Makefile. 7 6 8 7 The attached patch (relative to svn r130129), uses this approach to simplify the Portfile and use the perl5 portgroup to greatest advantage. … … 12 11 The post-patch phase then replaces the patched symbolic values with appropriate paths expected by the perl5 port group. Attempts to fixup DOC/Makefile have been removed because, although this Makefile is invoked during the install target, it does nothing because pre-generated copies of the HTML documentation are included in the distributed tarball. 13 12 14 Since everything that is done in the Makefile occurs during the execution of the install target, the build phase is disabled by replacing it 15 with a dummy version. Note that previous attempts to set the various user options by passing them as command line arguments in the build phase were ineffective since the Makefile hard codes these values and ignores any command line arguments. The complete install process now is invoked during the destroot phase only, using the user options specified during post-patch. 13 Since everything that is done in the Makefile occurs during the execution of the install target, the build phase is disabled by replacing it with a dummy version. Note that previous attempts to set the various user options by passing them as command line arguments in the build phase were ineffective since the Makefile hard codes these values and ignores any command line arguments. The complete install process now is invoked during the destroot phase only, using the user options specified during post-patch. 16 14 17 15 Because the installed file layout is changed from previous versions, the port revision is incremented.