svn commit: r493186 - in head/net: . p5-Net-Ping

[Po-Chuan Hsieh]

On Tue, Feb 19, 2019 at 3:30 PM Alexey Dokuchaev <danfe at freebsd.org> wrote:

> On Tue, Feb 19, 2019 at 07:54:53AM +0800, Po-Chuan Hsieh wrote:
> > On Mon, Feb 18, 2019 at 4:46 PM Alexey Dokuchaev <danfe at freebsd.org>
> wrote:
> > > On Sun, Feb 17, 2019 at 07:38:34PM +0000, Sunpoet Po-Chuan Hsieh wrote:
> > > > New Revision: 493186
> > > > URL: https://svnweb.freebsd.org/changeset/ports/493186
> > > >
> > > > Log:
> > > >   Add p5-Net-Ping 2.71
> > >
> > > Per MOVED, it was removed in 2016 because it's included in all
> supported
> > > versions of Perl, so what had happened since then?  It was not
> mentioned
> > > in the commit log.
> >
> > Like Kurt said, it's the newer version in CPAN. I think it's the same
> > reason why it's removed and now it's back.
>
> OK, so the plan is to remove it from Perl, or what?  Otherwise, I don't see
> why this situation won't repeat itself.


>From my point of view, keeping a Perl core module as a port depends on
several factors:
- the version in CPAN
- the version in supported Perl releases
- the version other ports depend on (if the version from lang/perl5.xx is
sufficient or not)

Therefore,
1. We may need a port if CPAN is newer than all or some supported Perl
releases.
2. A ports (from CPAN) can be removed if it is equivalent to or older than
that in all supported Perl releases.
3. The port may come back if the situation changes, e.g. Net::Ping in this
case.


> > In fact, I made it from scratch and at the last step, instead of "svn
> add",
> > I checked MOVED, svn copied the old one and replaced the whole directory
> > with mine. I didn't really read the diff. I could change it if you want.
>
> I don't insist, given your explanation.  It would be better if this would
> be made part of the commit log though.  Thanks for replying,
>
> ./danfe
>