> Sounds good to me, but I have a question. If one does :
>
>
> PerlSetINC /this/dir
>
>
>
> PerlSetINC /this/other/dir
>
>
> Can I assume that it would:
>
> 1. Populate @INC on a per-request/per-location basis ?
> 2. Allow for changes of @INC , like if the application code fiddles
On Tue, Nov 20, 2001 at 02:22:54PM +0800, Stas Bekman wrote:
> Doug MacEachern wrote:
>
> >On Mon, 12 Nov 2001, Stas Bekman wrote:
> >
> >
> >>this patch implements the PerlINC wrapper which does:
> >>s/PerlSwitches -Ilib=foo/PerlINC foo/
> >>
> >
> >if we add a new directive like this i think it
Doug MacEachern wrote:
> On Mon, 12 Nov 2001, Stas Bekman wrote:
>
>
>>this patch implements the PerlINC wrapper which does:
>>s/PerlSwitches -Ilib=foo/PerlINC foo/
>>
>
> if we add a new directive like this i think it should be a wrapper around
> what 'Perl{Set,Pass}Env PERL5LIB' would do, th
Doug MacEachern wrote:
> On Mon, 12 Nov 2001, Stas Bekman wrote:
>
>
>>this patch implements the PerlINC wrapper which does:
>>s/PerlSwitches -Ilib=foo/PerlINC foo/
>>
>
> if we add a new directive like this i think it should be a wrapper around
> what 'Perl{Set,Pass}Env PERL5LIB' would do, th
On Mon, 12 Nov 2001, Stas Bekman wrote:
> this patch implements the PerlINC wrapper which does:
> s/PerlSwitches -Ilib=foo/PerlINC foo/
if we add a new directive like this i think it should be a wrapper around
what 'Perl{Set,Pass}Env PERL5LIB' would do, that is:
- unshift @INC
- work per-direct
