OK, so I'd have to download the tarball from cpan.org, rather than using cpan / apt-get to install them? That's something I don't think I've tried before, but I think I can give it a go when I get home.

I think I'm a half-way decent coder, but I know very little about the internals or development of perl itself. I certainly don't have any idea if I have an SLA with module authors, let alone where it is or what it might say. I don't feel that I'm competent to patch the source code, and am only prepared to try this because it seems very simple. I certainly don't know how I would go about submitting a pull request. And I don't think those should be requirements for installing a module.

I don't feel unjustified in being frustrated that I've spent hours banging my head against a brick wall, when seems to be something that the maintainer could have fixed relatively quickly in the last six months. I'm not suggesting that all bugs need to be fixed within a week or anything like that, but if you have a major issue that literally stops the module from being installed, and it seems to be a relatively simple fix, and they can't find the time to deal with that within six months, then perhaps it needs to be considered abandoned and someone else take over. Perhaps that is unreasonable, I didn't get a lot of sleep last night, and my mood isn't the best. I'm trying to be fair, and I beg your indulgence if it's not coming off that way; I'm sure I'll be less short tomorrow.

And before someone suggests it, no I'm not volunteering. I don't have the skills or the understanding or the talent to even begin to take on such a project.

In reply to Re^4: cURL And XML breaking the install of a previosuly fine script by wintermute115
in thread cURL And XML breaking the install of a previosuly fine script by wintermute115

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.