MacPorts automake and python

[Brandon Allbery]

On Thu, Mar 20, 2014 at 4:27 PM, Daniel J. Luke <dluke at geeklair.net> wrote:

> for perl, there's a 'vendor' directory (where we install stuff) and a
> 'site' directory (where anything goes). If an end-user installs his/her own
> perl modules, they end up in the site directory (which is in $prefix).
>
> Of course, things could be much better for perl than the way we're doing
> things now, so maybe it's not the best example...
>

That is how Perl normally works, though... and how, to be honest, I'd
expect Python to behave. You need local configuration to change it.
(Possibly Perl makes this easier than Python does, though; that'd be Python
all over... One True Way instead of letting you configure it.)

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20140320/f45e8eca/attachment.html>