Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
One should surely put $(MAKE) test in both rules.xs and rules.noxs. They can be found in /usr/share/dh-make-perl/, but if you have them in ~/.dh-make-perl/, those will override the system wide files.

It's a shame that I don't know anything about Makefiles, 'cause it would be nice if we could capture and handle output like:
t/12_signals_ev.......skipped: the Event module is not installed
or:
Warning: prerequisite Array::RefElem failed to load: Can't locate Arra +y/RefElem....
OTOH, they're probably handled by dh-make-perl, so it must be possible to grab it somehow. (Yes, dh-make-perl itself is a perl program (duh :))

2;0 juerd@ouranos:~$ perl -e'undef christmas' Segmentation fault 2;139 juerd@ouranos:~$


In reply to Re: Leveraging Debian for Module Management by Juerd
in thread Leveraging Debian for Module Management by jwest

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.