develooper Front page | perl.perl5.porters | Postings from July 2014

Re: Criteria for becoming/dropping a core module [was: Re: maintainerwanted: Time::Piece]

Thread Previous | Thread Next
From:
Craig A. Berry
Date:
July 31, 2014 23:07
Subject:
Re: Criteria for becoming/dropping a core module [was: Re: maintainerwanted: Time::Piece]
Message ID:
CA+vYcVwODuf2K1aExrZmiro2AkF9=AGAbSDOrwONX6Z4YtS41w@mail.gmail.com
On Thu, Jul 31, 2014 at 6:51 AM, Neil Bowers <neil@bowers.com> wrote:
>
> On 30 Jul 2014, at 16:09, Jarkko Hietaniemi <jhi@iki.fi> wrote:
>
> Time::Piece was an attempt in ["best practice"]
>
>
> Though I'd like to squeeze in #4.5... "modules where tight bundling with
> core is necessary/useful", like the B::
>
> I'd be all for squeezing out all that do not pass #1-#4.  But backward
> compat: at what release would we set the "grandfather line"?
>
>
> So my updated hierarchy, given some of the comments yesterday:
>
>   1. Needed to install perl (Test::Harness)
>   2. Considered part of the language (strict/warnings)
>   3. Toolchain modules needed to bootstrap your installation (CPAN)
>   4. Dependencies for any of the above (HTTP::Tiny)
>   5. Modules for talking to your environment (Cwd, File::Spec*)

All of the #5s that I can think of offhand are needed to build perl
and run the test suite, so these are really part of #1.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About