[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:                                       
-------------------------------+--------------------------------------------
Comment (by vinc17 at macports.org):

 Replying to [comment:10 nox at macports.org]:
 > Nope. Perl core needs the getopt-long module. So we can't remove it
 > from perl5.8 files. Except if we do that in a post-destroot stage,
 > but that would be more of a workaround than a real bugfix.

 Yes, I meant at this stage. And I don't see this as a workaround.

 > As narf_tm said, that would be too difficult to maintain, even though
 > updates are not released __that__ often.

 Actually, I find it '''easier''' to maintain. Otherwise one has the
 following problem: Assume that some module M provided by the Perl core
 gets updated separately by upstream and a new port is added for this
 module to use this new version (as what happened for the getopt-long
 module). Then all the ports that use this module should be updated to
 depend on this new port (providing the new version of M). With the meta-
 port solution, ports using Perl could depend only on the meta-port and
 would not need to be updated whenever a new port providing a core module
 is added.

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