Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Non-standard Perl Module Locations
- Date: Wed, 12 Mar 2008 14:38:58 +0900
- From: "David Shanahan" <david@example.com>
- Subject: Re: [tlug] Non-standard Perl Module Locations
- References: <20080312033943.GF2019@lucky.cynic.net>
> For example, the ruby code is pretty > simple: > > d = QAM.dirs > $LOAD_PATH.unshift(d.rubylib_sitearch) > $LOAD_PATH.unshift(d.rubylib_site) > $LOAD_PATH.unshift(d.rubylib_arch) > $LOAD_PATH.unshift(d.rubylib) > ENV['PATH'] = d.release('bin') + ':' + ENV['PATH'] Almost identical with perl, just manipulate the @INC array. unshift @INC, $d->perllib_sitesearch(); unshift @INC, $d->perllib_site(); See what perl uses by default for library paths perl -e "print join(\"\\n\",@INC);" Similarly the %ENV hash is tied to the process environment. You could use the Env module to make manipulating path strings easier too. perldoc Env
- Follow-Ups:
- Re: [tlug] Non-standard Perl Module Locations
- From: steven smith
- References:
- [tlug] Non-standard Perl Module Locations
- From: Curt Sampson
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Freely distributable Japanese capable utf8 font?
- Next by Date: Re: [tlug] Non-standard Perl Module Locations
- Previous by thread: [tlug] Non-standard Perl Module Locations
- Next by thread: Re: [tlug] Non-standard Perl Module Locations
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links