(tye)Re: How to make a module aware of where it is installed?

chromatic said "lib" not "blib". Create a "lib" subdirectory at the top of your package and put any extra files to be installed in there with the proper directory structure.

For example, if you are building your module in /home/tye/Foo-Bar then you could have something like the following files:

/home/tye/Foo-Bar/MANIFEST
/home/tye/Foo-Bar/Makefile.PL
/home/tye/Foo-Bar/Bar.pm
/home/tye/Foo-Bar/lib/Foo/blurp.pm
/home/tye/Foo-Bar/lib/Foo/Bar/Baz.pm
[download]

and "make" would create the following files:

/home/tye/Foo-Bar/blib/lib/Foo/Bar.pm
/home/tye/Foo-Bar/blib/lib/Foo/blurp.pm
/home/tye/Foo-Bar/blib/lib/Foo/Bar/Baz.pm
[download]

and "make install" would then put them in the correct final location.

- tye

Comment on (tye)Re: How to make a module aware of where it is installed? Select or Download Code

Replies are listed 'Best First'.
Re: (tye)Re: How to make a module aware of where it is installed? by jaldhar (Vicar) on Dec 04, 2002 at 16:35 UTC
Ah ok I misunderstood. This makes my Makefile.Pl marginally simpler, but still doesn't solve the problem of the module itself knowing where it is installed. -- જલધર	[reply]
(tye)Re2: How to make a module aware of where it is installed? by tye (Sage) on Dec 04, 2002 at 16:43 UTC
If your module is called Foo::Bar, then $INC{"Foo/Bar.pm"} will give you the full path to your Bar.pm file. Or you could use __FILE__ for the same thing. Then use File::Basename and/or File::Spec (see also File::Spec) to get the path of just the directory. - tye	[reply]
Re: (tye)Re2: How to make a module aware of where it is installed? by jaldhar (Vicar) on Dec 04, 2002 at 16:51 UTC
Yep. that's what I do now based on atcroft's suggestion. -- જલધર	[reply]