Thanks Tom,
I agree that it aint a big deal to write a oneliner hacking the shebang
line, but, thought overriding some variables during the MakeMaker make would
be more cleaner. I looked around for some information and finally ended up
sending this mail.
In my make environment surrounding the DBI compilation, I have a perl script
which is used during 'make install' instead of default install binary. I
realized that MakeMaker will ignore such INSTALL variable overriding. The
ideal place for that onliner in my env is to be included in this install
perl script, but that will not work as I mentioned earlier. any ideas here
??
cheers
Mayuresh
On Dec 29, 2007 1:13 AM, Tom Phoenix <[EMAIL PROTECTED]> wrote:
> On Dec 28, 2007 12:39 AM, Mayuresh Nirhali <[EMAIL PROTECTED]>
> wrote:
>
> > During DBI building, MakeMaker uses the fixin() method to write the
> shebang
> > line for all the perl scripts that will be installed.
> > The path on my machine is /usr/perl/5.8.4/bin/perl. I also have
> > /usr/perl5/bin/perl which is *currently* pointing to the same 5.8.4perl,
> > but this generic version independent path helps me pointing to the
> latest
> > version all the time.
> >
> > I would like to have all the shebang lines replaced to the generic
> > /usr/perl5/bin/perl. Now, MakeMaker's fixin method seems to be
> > using $Config:{startperl}. If my understanding is right, startperl is
> > populated during installation (correct me if I am wrong here), Is there
> a
> > way to change this parameter to point to the version independent perl
> path
> > ??
>
> The value of $Config{startperl} comes from your Config.pm file, which
> in turn was built when your perl binary was built. In general, if you
> want Config.pm to say something different, you should rebuild and
> reinstall perl and everything that comes with it. If you've changed
> some of the really important things in Config.pm, you may need to
> rebuild some or all of the extra modules you've installed, too.
>
> On the other hand, that's a lot of work considering the result. (Do
> you want or need to alter the headings on scripts installed with perl
> or other modules?) You'll re-install hundreds of files, but only a few
> of them are only slightly changed. If you don't need to rebuild perl
> for another reason, you might be able to get away with merely editing
> the Config.pm file. That's not always appropriate, but in this case it
> might be the right answer.
>
> On the gripping hand, another right answer might be to hack up a
> utility to munge the shebang lines. How hard could it be? Somebody is
> probably making a one-liner to do that right now....
>
> Good luck with it!
>
> --Tom Phoenix
> Stonehenge Perl Training
>
--
Work like you don't need money !
Love like you've never been hurt !!
Dance like noone's watching you !!!
