Yitzchak Scott-Thoennes wrote:
> I somehow missed this last paragraph earlier.  I disagree; there's no
> reason to delay working on integrating M::B just because the same is
> happening for CPANPLUS.  (All the more so now that CPANPLUS integration
> has run into the rock of portable subprocess handling.)

Right.

> Ken, Rafael (and others), I'm going to work on integration of
> ExtUtils::{CBuilder,ParseXS}.  So far, looks like the tests need some
> tweaking to work in the perl core, and Ilya's xsubpp patch needs to
> be added to ParseXS.pm.  When I have things working, I'll first send
> patches to the CPAN distributions for Ken to eyeball, and then a patch
> to perl to add what should be identical files to the core.

OK.

> As far as M::B itself goes, I'd say the 0.27 branch should get added to
> core ASAP, even though there is ongoing work being done on it.  Let's
> get the ball rolling, here.  There's no reason further changes can't
> be added as they come.
> 
> Optionally, perhaps Ken would appreciate commit access for perl so he
> can keep bleadperl up to date with M::B development periodically?

Well, why not, but I don't see this as necessary -- the build process of
perl doesn't use M::B so there's nothing critical here.

-- 

Reply via email to