Yes, the module structure is correct under blib/lib. The problem is the main module itself has to know what blib/lib expands to. For instance under perl 5.8 on Debian GNU/Linux,
The INSTALLDIRS variable in Makefile.PL determines which one gets used or it defaultes to site. It will translate instances of blib/lib in the Makefile itself but doesn't do that elsewhere without the PM_FILTER.INSTALLPRIVLIB='/usr/share/perl/5.8.0' INSTALLSITELIB='/usr/local/share/perl/5.8.0' INSTALLVENDORLIB='/usr/share/perl5'
What I am doing for now is:
but there has to be a better solution than this.'PM_FILTER' => 'perl -pe \" if (\"$(INSTALLDIRS)\" eq \"perl\") { s|INST_LIBDIR|$(INSTALLPRIVLIB)|g; } elsif (\"$(INSTALLDIRS)\" eq \"vendor\") { s|INST_LIBDIR|$(INSTALLVENDORLIB)|g; } else { s|INST_LIBDIR|$(INSTALLSITELIB)|g; } \"'
--
જલધર
In reply to Re: Re: How to make a module aware of where it is installed?
by jaldhar
in thread How to make a module aware of where it is installed?
by jaldhar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |