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: Thu, 13 Mar 2008 17:02:53 +0900
- From: "David Shanahan" <david@example.com>
- Subject: Re: [tlug] Non-standard Perl Module Locations
- References: <20080312033943.GF2019@lucky.cynic.net> <47D7FED6.4090105@sonic.net> <20080312151121.U1693@plexi.pun-pun.prv> <47D7721F.7080107@sonic.net> <82c89d700803112238p2f67a262red145f8c1184b881@mail.gmail.com> <20080313065737.GC1789@lucky.cynic.net>
> Thoughts? You have probably already considered this but... Would building a perl interpreter specifically for the project / environment you are trying to control be out of the question ? That way you could configure the build paths at compile time for the perl binary (just by specifying a prefix), replace this perl Makefile.PL PREFIX=/a/b/c/release with this /a/b/c/release/bin/perl Makefile.PL And not need to require qam.pl in any scripts. But you would have to change the interpreter used on all your scripts.
- References:
- [tlug] Non-standard Perl Module Locations
- From: Curt Sampson
- Re: [tlug] Non-standard Perl Module Locations
- From: steven smith
- Re: [tlug] Non-standard Perl Module Locations
- From: Tod McQuillin
- Re: [tlug] Non-standard Perl Module Locations
- From: steven smith
- Re: [tlug] Non-standard Perl Module Locations
- From: David Shanahan
- Re: [tlug] Non-standard Perl Module Locations
- From: Curt Sampson
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Apache MPM performance
- Next by Date: Re: [tlug] Non-standard Perl Module Locations
- Previous by thread: Re: [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