Keep It Simple, Stupid | |
PerlMonks |
Setting the path when a module installsby arcnon (Monk) |
on Jan 04, 2006 at 23:13 UTC ( [id://521050]=perlquestion: print w/replies, xml ) | Need Help?? |
arcnon has asked for the wisdom of the Perl Monks concerning the following question:
what is the best practice for setting the path of a library if it isn't in their path?
warn them to set the path? try and set it myself like: `set path=($path /usr/local/bin)`; or `PATH=${PATH}:/usr/local/bin`; Is their a standard for this type of thing when writing a module? edit: sorry that I wasn't specific enough... On OSX when you install allegro the path to the conf file is at /usr/local/bin/allegro-config When you try and install the perl allegro pm it can't find this file because it isn't in the path. I thought I might write a patch for it. That why I am interested in what is the best practice for this type of thing. So makefile.pl can suck the info it needs and I do it the right way.
Back to
Seekers of Perl Wisdom
|
|