Front page | perl.perl5.porters |
Postings from February 2013
On Thu, Feb 14, 2013 at 10:10 AM, Nicholas Clark <nick@ccl4.org> wrote: > 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 > You know this better than I do, I was just throwing in my thoughts. Please continue this discussion in a new thread if you want to have it now, thanks!Thread Previous | Thread Next