Re: [Module::Build] M::B and no_index

[Ken W. <ke...@ma...>]

On Apr 24, 2006, at 12:44 AM, Randy W. Sims wrote:
> I'm not sure what to do about this one.
>
> 1.) We can strictly record the @INC at the time 'Build.PL' is run,  
> we can check it against @INC when './Build' is run, and if it is  
> different, we can warn the user. CON: User cannot take advantage of  
> changes to @INC /after/ running 'Build.PL' without re-running it.
>
> 2.) We can add any changes to @INC to the beginning or the end of  
> the original @INC. This will allow the user to add entries either  
> with -I option or by setting env PERL5LIB, etc. CON: Do the uniq  
> entries go at the beginning or end; there is no clear choice.
>
> I'm leaning heavily on (1) at the moment because it is well defined  
> and we alread warn about other changes in the environment. Also, I  
> don't see much advantage to have a differing @INC between  
> 'Build.PL' and './Build', so nothing is lost.

The original use case for all this @INC munging is that when the  
author puts a "use lib" or a "push @INC" or whatever in their  
Build.PL script, the effect on @INC ought to be seen in the Build  
script too.

That means that a strict interpretation of (1) isn't workable.  It  
would also break backwards compatibility with existing Build.PL scripts.

If we can't figure out some smart version of (2) that we like, we  
should just defer this to a later version and not try to fix it for  
0.28.

  -Ken