G'day thanos1983,

"So first thing first. The module code if someone want to test it can be found here RFC: Net::SNTP::Client v1."

That link has two problems (which you should fix):

  1. It doesn't link to "RFC: Net::SNTP::Client v1" at all. In fact, it links to The Monastery Gates! So, at this point, nobody can see the code, let alone test it (sure, we could spend time searching for it, but we shouldn't have to).
  2. It's an absolute link to 'http://perlmonks.com/?' — anyone following it stands a good chance of being logged out. Don't use absolute links, use relative links. See "All Links Within PerlMonks Should Be Relative" for both the reason why and how to do this.
"I was following the instructions from How to make a CPAN Module Distribution ..."

[That's also an absolute link, so please fix it as well.]

"How to make a CPAN Module Distribution" is thirteen (13) years old: I'm not suggesting there's wrong information there, it's just old information. It shows three methods: h2xs, ExtUtils::ModuleMaker and Module::Starter: you haven't said which one you're using. Take a look at "perlnewmod: Perl modules: preparing a new module for distribution" — this forms part of the core Perl distribution and should be (more) current.

"I have post several questions over and over ..."

In one of these (Undefined subroutine &main [SOLVED]), you said you had installed Module::Starter and thought it was causing the errors (described in that thread) but, as it turned out, it had nothing to do with those errors. I recommend you go back to using Module::Starter: it does a lot of the work for you including, via your chosen plugin, creating a distribution bundle suitable for uploading to CPAN.

I've been using Damian Conway's Module::Starter::PBP plugin for about eight years. I've used it successfully in large commercial contracts and for smaller, personal (hobby) projects. While I'm happy to recommend it, I certainly don't insist you use it: there's other Module::Starter Plugins which you may find preferable.

"I am trying to install the module manually ..."

I think you're completely jumping the gun doing this. At its most basic, my typical workflow is:

  1. perl Makefile.PL make make test
  2. Add/Change/Delete module/test code.

    make realclean

    Go to 1.

That cycle will repeat many, many times before I get to 'make dist' or 'make install'.

-- Ken


In reply to Re: Failed test of Net::SNTP::Client module by kcott
in thread Failed test of Net::SNTP::Client module by thanos1983

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.