[MacPorts] #36980: perl5.14 sitebin & vendorbin flags may be inapproriate

[MacPorts]

#36980: perl5.14 sitebin & vendorbin flags may be inapproriate
-----------------------+---------------------
  Reporter:  derek@…   |      Owner:  ricci@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.1.2
Resolution:            |   Keywords:
      Port:  perl5.14  |
-----------------------+---------------------

Comment (by bruce.miller@…):

 Well, forget the part about perl. Imagine you compiled a program using c,
 or wrote a script using
 bash, or Language Of Your Choice.  Now, suddenly, when you run make
 install on your project,
 your program doesn't go to /usr/bin, or /opt/bin or whatever.  No, it goes
 into
 /opt/mysterious/glib-1.27/sitebin, or
 /opt/somewhereelse/bash-9.99/libfoobin.
 Most users can't find it.  And if they do, should they put this crazy path
 into their {{{$PATH}}}? And update it everytime something changes at
 macports?
 And this, when you didn't even ''request'' a specific version of c, bash,
 perl, or whatever!

 I'm trying not to get snarky, and I sympathize with the desire to support
 multiple
 versions. And I really do appreciate the work you guys are doing.

 But you really can't just change the installation path to something
 version dependent, but provide no mechanism, tool or even suggestions of
 how to work around this.

 I've used the standard build mechanism for packages in Perl, and it was
 nice
 that it worked on the Mac (I don't use one, but I have colleagues who do).
 I don't have a lot of opportunity to experiment with random, macports-
 specific,
 hacks on the build to try to work around this.

 So, again, ''please'': How should I modify my Makefile.PL so that it works
 in MacPorts?

 Thank you;

-- 
Ticket URL: <https://trac.macports.org/ticket/36980#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS