develooper Front page | perl.perl5.porters | Postings from February 2013

Re: perlopentut modernization

Thread Previous | Thread Next
From:
Nicholas Clark
Date:
February 14, 2013 09:10
Subject:
Re: perlopentut modernization
Message ID:
20130214091029.GU5653@plum.flirble.org
On Thu, Feb 14, 2013 at 10:01:41AM +0100, Alexander Hartmaier wrote:
> On Thu, Feb 14, 2013 at 7:11 AM, Nicholas Clark <nick@ccl4.org> wrote:

> > I'll repeat though, that the core distribution doesn't need to install and
> > modules only used for testing. (Or for building, for that matter).
> >
> > Nicholas Clark
> >
> That's a author_requires/build_requires in my opinion. Is it a problem that
> Perl requires non-core modules for it's test suite? Do author-only tests
> exist at the moment? Cause the whole pod checking is nothing a user should
> have to run on install imho.

The distribution in git *is* the distribution for the authors. The continuous
integration environment (the smoke testers, and Jenkins) need to verify that
changes are valid.

We're also not talking about a *module* here - the distribution needs to
bootstrap without using an installed Perl, because we can't assume that one
is there. (Our pre-requisites *can* cross-build. We can't. So we can't get
to a new platform or architecture by bootstrapping on one on which Perl does
work. New architectures are real - I think Linux has recently added two.)

So everything used during the development cycle needs to be in the core git
checkout.

So, whilst yes, technically it doesn't have to be in a tarball distribution,
it has to be pretty much everywhere else, meaning that the distinction is
moot.

Nicholas Clark

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