<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 20, 2014 at 4:27 PM, Daniel J. Luke <span dir="ltr"><<a href="mailto:dluke@geeklair.net" target="_blank">dluke@geeklair.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">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).<br>
</div>
<br>
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...<br></blockquote><div><br></div><div>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.)</div>
<div> </div></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>