Hi Andrew,
Andrew Fresh wrote on Wed, Oct 30, 2013 at 01:50:56PM -0700:
On Wed, Oct 30, 2013 at 08:31:58PM +0100, Ingo Schwarze wrote:
-'DISTRIBUTION' = 'DAGOLDEN/Module-Build-0.39_01.tar.gz',
+'DISTRIBUTION' = 'LEONT/Module-Build-0.4007.tar.gz',
It's only 4.003 in 5.18, not sure if that makes a difference,
That would be sufficient to appease CPAN modules requiring =0.40,
but it wouldn't include three-argument-open(3p), and it lacks a few
minor bug fixes and enhancements.
but this patch would need to be ported forward if we move to newer
versions of perl.
I see your point. Right now, i feel unable to judge how much
inconvenience that might cause, and which is the better way.
https://github.com/Perl/perl5/tree/maint-5.18/cpan/Module-Build
Module::Build will be deprecated as a core module in 5.20 (May 2014) and
removed in 5.22 (I guess May 2015).
http://www.dagolden.com/index.php/2140/paying-respect-to-modulebuild/
Oh well. To paraphase (forgive me if i misunderstand), It ought to
be easy to write something better than Module::Build, and even though
nobody has so far volunteered to propose an actual design, and even
less to write some code, we already have a definite time schedule for
retiring Module::Build. WT...?
However, whetever thay do, we are certainly able to cope, either just
keeping Module::Build in base or moving it to a port, whatever will be
more convenient when the time comes.
Post vBSDcon I have most existing patches working with 5.18.1,
I have serious doubts that i'm experienced enough to manage a
complete Perl update; certainly not without help from more experienced
developers. However, i'm currently having a look at your work
before making up my mind about what to propose for proceeding with
the update to Module::Build or even Perl as a whole.
the only failing so far is that with threads enabled t/op/threads-dirh.t
fails.
(mv patches/{APPLIES,GOOD}/use_threads.patch)
This test appears to point to a failure that needs fixing but I am not
skilled enough to know how.
I'll try to look at it - even though i know almost nothing about
threads so far. But maybe we can find someone to help with this
specific detail, if that's really the main remaining hurdle.
https://github.com/afresh1/OpenBSD-perl
Would it be preferred to plan ahead for removal and to somehow do this
update in the ports tree?
I don't think so. Even when we update to 5.18, Module::Build is still
in base, and i don't see any reason to move it out even earlier than
upstream will (maybe) do it. Which version of Module::Build we update
to is an orthogonal question, anyway.
If upstream sticks to their plan (even tough it still seems vague to me),
then right before merging perl-5.22 to OpenBSD base would be the right
time to decide whether we want to keep Module::Build in base, or to set
up a port at that point in time.
Other than that, the changes that I saw in that patch didn't look scary
to me and I would be happy to use the updated version, three argument
open seems like a good improvement.
Good, thank you. If i come to the conclusion that we cannot upgrade
to perl 1.18 right now, i will consider how to proceed with
Module::Build only, for now.
Yours,
Ingo
