I fail to see how not installing LWP will make your script more portable. Bundle LWP with your script when you distribute it if necessary. A reliance on things like 'lynx' is precisely what we're trying to avoid by using modules in the first place.

Your problem with your two system calls is probably because 'lynx' isn't in the script's path. Specify an absolute filename to the program or update your PATH accordingly.

If you "can't" install a module, you might just consider using IO::Socket and request the page by hand using Perl's native network support. That would be the "most" portable solution, but obviously you're never going to code yourself a solution that's as robust as using LWP in the first place will be.

In reply to Re: getting HTML source by Fastolfe
in thread getting HTML source by ColonelPanic

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.