Re: [Module::Build] Help: Module::Build V 0.21 under WinXP
Status: Beta
Brought to you by:
kwilliams
|
From: Randy W. S. <Ra...@Th...> - 2003-11-06 23:09:15
|
On 11/6/2003 4:11 PM, Randy W. Sims wrote: > On 11/6/2003 1:16 AM, Ron Savage wrote: > >> On Thu, 06 Nov 2003 00:38:24 -0500, Randy W. Sims wrote: >> >> Hi Randy >> >> >>> That should be 'codebase', and that should be given on the command >>> line >>> for the ppd target. >>> >>> perl Build ppd codebase="./x86/CGI-Explorer-2.02.tar.gz" >> >> >> >> OK. >> >> The output is: >> -----><8----- >> <IMPLEMENTATION> >> <CODEBASE HREF="./x86/CGI-Explorer-2.02.tar.gz" /> >> </IMPLEMENTATION> >> -----><8----- >> whereas it should look like (this is downloaded from Randy Kobe's site): >> -----><8----- >> <IMPLEMENTATION> >> <OS NAME="MSWin32" /> >> <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8" /> >> <CODEBASE >> HREF="http://theoryx5.uwinnipeg.ca/ppms/x86/Module-Build.tar.gz" /> >> </IMPLEMENTATION> >> -----><8----- > > > I've taken a quick look a Dave's code, and it seems to me it is doing > the right thing. If there is no XS code, it assumes that this is a > cross-platform module, so it omits the OS & ARCHITECTURE tags. Does ppm > fail without those tags? > >>> For the errors, try updating your version of Archive::Tar from: >>> >>> <http://p4.elixus.org/snap/Archive-Tar.tar.gz> >> >> >> That version makes a difference: >> >> But CGI-Explorer-2.02.tar.gz does not contain any paths :-(. > > > Ok. I'll try to look into this tonight. I seem to recall running into > this problem in some script I wrote a while back. Does this occur only > on Windows... > > Randy. > I played around with this for about 30-45 min. before realizing it works. I bet your using a program like WinZip to look at the archive; it apparently doesn't always read the tar format correctly. I use a port of tar on Windows. (Can't remember where I got it; my usual source for ports is <http://sourceforge.net/project/gnuwin32>, but that tar is broken. I will email it upon request.) You might wish to check with the authors/maintainers of your archive program and/or Archive::Tar for full compatiblity info. As far as the ppd output, Dave's implementation is correct according to the OSD specification <http://www.w3.org/TR/NOTE-OSD.html>. Note in section 4, the first example shows an IMPLEMENTATION section that is OS dependent first which includes an OS element followed by an IMPLEMENTATION section for any OS which does not include an OS element. PPM is supposed to follow the OSD spec. If it does not work correctly, try the ppm mailing list <http://listserv.ActiveState.com/mailman/listinfo/ppm>. HTH, Randy. -- A little learning is a dang'rous thing; Drink deep, or taste not the Pierian spring; There shallow draughts intoxicate the brain; And drinking largely sobers us again. - Alexander Pope |