Re: [Module::Build] Fwd: CPAN Upload: Y/YV/YVES/ExtUtils-Install-1.38.tar.gz
Status: Beta
Brought to you by:
kwilliams
From: Randy W. S. <ml...@th...> - 2006-04-10 08:11:36
|
demerphq wrote: > On 4/10/06, Randy W. Sims <ml...@th...> wrote: >>It's a bug in Archive::Tar that we were not able to resolve with the >>maintainer. The directories are there, but some Windows programs can't >>see them: WinZip, older versions of WinRAR, etc. GNU tar on *nix and >>Cygwin can read them. The newest WinRAR can. Maybe 7-zip? > > > Ok it didnt occur to me it might be a problem with winzip, so ill > investigate using other tools. I also noticed that the tar/gzip > produced by EUMM was about 5-10k smaller. But IMO having a problem > with Winzip is a pretty big problem. :-) Yup. > And to be honest im not so sure about using Archive::Tar as a first > option. I recall from previous times looking at it that its horribly > inefficient when dealing with larger file sizes (possibly this has > been resolved). IMO it would probably be preferable to let tar do the > work if its available. Is there some way I can tell MB that i would > prefer that it use a shell tool instead of pure perl stuff? (Im > cheating here, as i havent looked at the docs of MB to see if an > answer is there :-) Is there a tar program that works on Windows? I've tried quite a few but could find any that could /create/ an archive on Windows, other than with Cygwin. perl Build dist --tar C:\bin\tar.exe --gzip C:\bin\gzip.exe >>I don't know how to resolve this issue. Since Archive::Tar is now in >>perl core, it may be worth bringing up there? Other tar programs, like >>GNU tar, create archives that work correctly in any archive tool. > > > Once i understand the problem I definately will bring it up with the > maintainers. Im pretty sure this wasnt a problem in older versions. <http://thread.gmane.org/gmane.comp.lang.perl.modules.module-build/282/> <http://thread.gmane.org/gmane.comp.lang.perl.modules.module-build/677/> >>>So all I did was a >>> >>> nmake dist >>> >>>So regarding the executable bits being set, my assumption is that >>>tar/gzip when run from the cmd.exe shell gets permissions wrong? >> >>I never really noticed this before. Will have to check into it. Windows >>doesn't have equivelant file modes, but I would expect it to err on the >>side of leaving the executable bit unset... > > > Ive not noticed it specifically either, but that doesnt mean anything. > I have experienced _general_ odd problems with unpacking files > sometimes. Some compression tools manage to pack the files so when i > unpack them they have Win32 ownership rights for people who arent > registered on my machine, meaning i have to retake ownership of them > before I can use them, ive also seen odd attributes being applied for > no apparent reason. Ive never bothered to look into it deeper than how > to override the problem tho. I'll need to investigate this at some point for Module::Build. See what happens when dist is run on Windows... Randy. |