[MacPorts] #12710: perl5 portgroup should be able to write in privlib dir for the bundled modules

[MacPorts]

#12710: perl5 portgroup should be able to write in privlib dir for the bundled
modules
-------------------------------+--------------------------------------------
  Reporter:  nox at macports.org  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect            |      Status:  new                                  
  Priority:  Normal            |   Milestone:  MacPorts base enhancements           
 Component:  base              |     Version:                                       
Resolution:                    |    Keywords:                                       
-------------------------------+--------------------------------------------
Changes (by narf_tm at macports.org):

 * cc: narf_tm at macports.org (added)

Comment:

 I still do not think we should be forcing Perl modules to replace Perl
 core modules.
 I also do not think that removing files from Perl is a decent option.
 This mean every time a core module gets updated, the Perl port is going to
 have to be modified to accommodate the newer module port.

 Why don't we do what the Perl INSTALL file suggests?

 {{{
 There is one other way of adding paths to @INC at perl build time, and
 that is by setting the APPLLIB_EXP C pre-processor token to a colon-
 separated list of directories, like this

        sh Configure -Accflags='-DAPPLLIB_EXP=\"/usr/libperl\"'

 The directories defined by APPLLIB_EXP get added to @INC I<first>,
 ahead of any others, and so provide a way to override the standard perl
 modules should you, for example, want to distribute fixes without
 touching the perl distribution proper.  And, like otherlib dirs,
 version and architecture specific subdirectories are also searched, if
 present, at run time.
 }}}

 We can use FreeBSD's Perl port as a good example of this.
 ==
 http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/perl5.8/Makefile?rev=1.94
 ==

 {{{
 BSDPAN_DEST=    ${PREFIX}/lib/perl5/${PERL_VER}/BSDPAN
 -Dccflags=-DAPPLLIB_EXP=\"${BSDPAN_DEST}\"
 }}}

 Call it what ever you want and use that path for the Perl ports instead of
 vendor.
 This seems like the most logical and sane solution to me.
 It is also the solution most other *nix distros seem to have used.

 Can we open this option up for discussion?

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/12710#comment:7>
MacPorts </projects/macports>
Ports system for Mac OS