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

Re: [PATCH] On eliminating external tools from the release process

Thread Previous | Thread Next
From:
David Golden
Date:
April 4, 2013 18:34
Subject:
Re: [PATCH] On eliminating external tools from the release process
Message ID:
CAOeq1c8x1mqOsTbKqvsCuDQiw9cBNVe0OjSqJDapYS-2P5+-9A@mail.gmail.com
On Thu, Apr 4, 2013 at 6:44 AM, Nicholas Clark <nick@ccl4.org> wrote:

>> > Ultimately, for the release process, we care about elapsed operator time,
>> So performance does matter during the build process?
>
> You've snipped the part where I said that other parts of the process will
> consume more time. That is a material part of my point.
>
> Optimise the slow parts. This won't be one of them.

It depends.  Don't we copy to a temp directory for making the archive
file?  If every file is copied with EU::Command as a separate command,
that means invoking Perl once per copy.  That is going to be very,
very slow on Windows.

This is a known issue with EU::MM on windows even just for ordinary
CPAN modules -- all the copies to blib and thence to site_lib need an
invocation of Perl per copy operation.  There's been talk of replacing
it with native OS commands, but no one has done the work.

EU::Command needs to be used *carefully* if the number of operations is large.

David

--
David Golden <xdg@xdg.me>
Take back your inbox! → http://www.bunchmail.com/
Twitter/IRC: @xdg

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