1 |
Since I don't see where anyone else has replied... |
2 |
|
3 |
we tend to prefer putting things in the vendor lib, its read high on the |
4 |
@INC list but won't overwrite other modules installed as part of the core |
5 |
install. The easiest way to get the path for this on a target host is |
6 |
something like |
7 |
|
8 |
eval `perl -V:installvendorlib` |
9 |
PERL_VENDOR=${installvendorlib} |
10 |
|
11 |
or something to that affect... |
12 |
|
13 |
On Wed, Jun 09, 2004 at 10:06:14AM +0200, Torsten Veller wrote: |
14 |
> i am writing an ebuild for a package that contains a perl script. The Makefile |
15 |
> says: |
16 |
> # Perl module |
17 |
> perlmoddir = $(datadir)/perl5 |
18 |
> |
19 |
> So the .pm file will be installed in '/usr/share/perl5'. |
20 |
> |
21 |
> Should i move this perl module to another directory? Which? Which tools help |
22 |
> me spotting the perl dir? |
23 |
> TIA |
24 |
> |
25 |
> -- |
26 |
> .: Torsten | Elegance and truth are inversely related. :. |
27 |
> |
28 |
> -- |
29 |
> gentoo-dev@g.o mailing list |
30 |
> |
31 |
> |
32 |
|
33 |
-- |
34 |
|
35 |
-----o()o--------------------------------------------- |
36 |
Michael Cummings | #gentoo-dev, #gentoo-perl |
37 |
Gentoo Perl Dev | on irc.freenode.net |
38 |
-----o()o--------------------------------------------- |