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.

In reply to Setting the path when a module installs by arcnon

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.