From: Uri Guttman >>>>>> "BM" == Bob McConnell <r...@cbord.com> writes: > > BM> To remove the tar binary from Config.pm: > BM> 1) Open C:\camelbox\lib\CPAN\Config.pm in an editor that understands > BM> Unix files (NOT notepad.exe; wordpad will work for this) > BM> 2) Find the line that says 'tar' => q[C:\\camelbox\\bin\\tar.EXE] and > BM> remove the tar.EXE command; the tar command should look like this when > BM> you're done: > > BM> 'tar' => q[], > > BM> CPAN will then switch to using Archive::Tar when you go to > BM> download/install modules. > > that implicates the tar.exe in your box as the guilty party. put the > blame on camelbox for not handling some variation in tar headers that > all other tar utils and modules can handle. report this as a big bug to > them.
Sorry Uri, but I don't agree with any of that. The way I see it: there is a bug in the program building those tar files that is erroneously splitting the path between the prefix and name fields in the headers. The Archive::Tar module handles the resulting corrupted files, but it is still abuse of the file structure. If they were built correctly, the GNU tar (and WinZIP) would still be able to extract them. A Camelbox developer provided the workaround via their mailing list, so they are aware of it. But I haven't looked at this year's Summer of Code projects, so I don't know if they will be working on it or not. Bob McConnell -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
