Skip to content
This repository

running multiple concurrent cpanm processes corrupts build.log #157

Closed
doy opened this Issue · 6 comments

4 participants

Jesse Luehrs Tatsuhiko Miyagawa mattn A.J. Lucas
Jesse Luehrs
doy commented

I do this occasionally when installing modules into multiple different perls. The issue is that cpanm writes to ~/.cpanm/build.log directly, and then just copies it into the proper place in ~/.cpanm/work/ once the process finishes. It seems like a better idea here would be to create ~/.cpanm/build.log as a symlink to the appropriate file in ~/.cpanm/work/ when the cpanm process starts, and then write to the file under ~/.cpanm/work/ directly.

Tatsuhiko Miyagawa
Owner

Sounds good to me. This will fix the issue on Win32 where two instances can't write to one file.

mattn
mattn commented

win32 don't have symlink. how about copy the file when finished for win32?

Tatsuhiko Miyagawa
Owner

It may not have a symlink but we actually do symlink already for latest-build.

mattn
mattn commented

Ah, it seems that symlink behave same as copy on win32. hehe.

A.J. Lucas

Hi guys, has anyone written a patch for this yet? I can try writing one if there are no volunteers.

Tatsuhiko Miyagawa
Owner

You can always give it a try :)

Tatsuhiko Miyagawa miyagawa closed this in #264
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.