Front page | perl.perl5.porters |
Postings from January 2009
Re: a plan for ext/
Thread Previous
|
Thread Next
From:
David Golden
Date:
January 24, 2009 20:58
Subject:
Re: a plan for ext/
Message ID:
5d4beb40901242058j293a319oef8711cc7dc5e557@mail.gmail.com
On Sat, Jan 24, 2009 at 4:57 PM, Nicholas Clark <nick@ccl4.org> wrote:
> However, one problem I thought that we might hit is (effectively) "early"
> and
> "late" extensions, where "early" would be anything that is part of the
> toolchain needed to bootstrap the build of extension modules, and should be
> completely built "early" (and installed to lib/) before running the
> Makefile.PL of most everything else.
>
What about just having a manifest-like file with an ordered list of ext/* to
build? It should change relatively infrequently so it's just the one-time
pain to figure out the key dependencies and move them up in the build
order. (This would work not unlike a Bundle, actually.)
More radically, perhaps, I believe CPAN.pm only requires File::Spec,
File::Temp, Scalar::Util, Test::Harness and Test::More (and File::HomeDir on
Darwin). So if those can get bootstrapped, then potentially CPAN.pm could
be used to build up everything else. On the one hand, that may be more
complicated than make_ext, but on the other hand, the less difference
between installing a dual-life module during core build versus afterwards,
the better.
-- David
Thread Previous
|
Thread Next