Thread: [Module::Build] Help: Module::Build V 0.21 under WinXP
Status: Beta
Brought to you by:
kwilliams
Menu
▾
▴
module-build-general
|
From: Ron S. <ro...@de...> - 2003-11-06 03:53:57
|
Hi Folks
I'm trying to replace my module Module::MakeDist with Module::Build,
and have a problem with 'Build dist'.
Build.PL:
-----><8-----
use Module::Build;
Module::Build -> new
(
=09code_base=09=09=3D> './x86/CGI-Explorer-2.02.tar.gz',
=09dist_abstract=09=3D> 'A CGI support module for tree management and
display',
=09dist_author=09=09=3D> 'Ron Savage <ro...@sa...>',
=09license=09=09=09=3D> 'artistic',
=09module_name=09=09=3D> 'CGI::Explorer',
) -> create_build_script();
-----><8-----
MANIFEST:
-----><8-----
Build.PL
Changes.txt
MANIFEST
META.yml
css/xtree.css
examples/bootstrap-hobbit.pl
examples/hobbit-hash.cgi
examples/hobbit.cgi
images/I.png
images/L.png
images/Lminus.png
images/Lplus.png
images/T.png
images/Tminus.png
images/Tplus.png
images/blank.png
images/current.png
images/custom.png
images/file.png
images/foldericon.png
images/new.png
images/open.png
images/openfoldericon.png
images/shut.png
js/xtree.js
lib/CGI/Explorer.pm
t/test.t
test.pl
-----><8-----
Current dir:
-----><8-----
C:\perl-modules\CGI-Explorer-2.02>dir
Volume in drive C has no label.
Volume Serial Number is 0810-E2D1
Directory of C:\perl-modules\CGI-Explorer-2.02
06/11/2003 02:46 PM <DIR> .
06/11/2003 02:46 PM <DIR> ..
06/11/2003 01:59 PM 313 Build.PL
06/11/2003 01:46 PM 4,463 Changes.txt
20/10/2003 10:45 AM <DIR> css
20/10/2003 10:45 AM <DIR> examples
20/10/2003 10:45 AM <DIR> images
20/10/2003 10:45 AM <DIR> js
06/11/2003 02:30 PM <DIR> lib
20/10/2003 11:22 AM 748 Makefile.PL
06/11/2003 02:38 PM 478 MANIFEST
06/11/2003 02:12 PM 83 MANIFEST.SKIP
06/11/2003 02:38 PM 282 META.yml
20/10/2003 10:45 AM <DIR> t
20/10/2003 11:22 AM 658 test.pl
7 File(s) 7,025 bytes
8 Dir(s) 12,099,035,136 bytes free
-----><8-----
Output:
-----><8-----
C:\perl-modules\CGI-Explorer-2.02>perl Build.PL
Checking whether your kit is complete...
Looks good
Creating new 'Build' script for 'CGI-Explorer' version '2.02'
C:\perl-modules\CGI-Explorer-2.02>perl Build
lib/CGI/Explorer.pm -> blib\lib/CGI/Explorer.pm
Manifying blib\lib/CGI/Explorer.pm -> blib\libdoc\CGI.Explorer.3
C:\perl-modules\CGI-Explorer-2.02>perl Build manifest
C:\perl-modules\CGI-Explorer-2.02>perl Build test
test.....ok
t\test...ok
All tests successful.
Files=3D2, Tests=3D2, 0 wallclock secs ( 0.00 cusr + 0.00 csys =3D 0.00
CPU)
C:\perl-modules\CGI-Explorer-2.02>perl Build install uninst=3D1
Skipping C:\Perl\site\lib\CGI\Explorer.pm (unchanged)
Skipping C:\Perl\man\man3\CGI.Explorer.3 (unchanged)
C:\perl-modules\CGI-Explorer-2.02>perl Build distcheck
C:\perl-modules\CGI-Explorer-2.02>perl Build dist
Deleting META.yml
mkdir CGI-Explorer-2.02
mkdir CGI-Explorer-2.02/images
mkdir CGI-Explorer-2.02/examples
mkdir CGI-Explorer-2.02/css
mkdir CGI-Explorer-2.02/t
mkdir CGI-Explorer-2.02/lib
mkdir CGI-Explorer-2.02/lib/CGI
mkdir CGI-Explorer-2.02/js
Creating CGI-Explorer-2.02.tar.gz
Unable to add file: 'CGI-Explorer-2.02' at
C:\Perl\site\lib/Module/Build/Base.pm line 1706
Unable to add file: 'CGI-Explorer-2.02/t' at
C:\Perl\site\lib/Module/Build/Base.pm line 1706
Unable to add file: 'CGI-Explorer-2.02/lib' at
C:\Perl\site\lib/Module/Build/Base.pm line 1706
Unable to add file: 'CGI-Explorer-2.02/lib/CGI' at
C:\Perl\site\lib/Module/Build/Base.pm line 1
706
Unable to add file: 'CGI-Explorer-2.02/js' at
C:\Perl\site\lib/Module/Build/Base.pm line 1706
Unable to add file: 'CGI-Explorer-2.02/images' at
C:\Perl\site\lib/Module/Build/Base.pm line 17
06
Unable to add file: 'CGI-Explorer-2.02/examples' at
C:\Perl\site\lib/Module/Build/Base.pm line
1706
Unable to add file: 'CGI-Explorer-2.02/css' at
C:\Perl\site\lib/Module/Build/Base.pm line 1706
Deleting CGI-Explorer-2.02
-----><8-----
Any ideas?
TIA.
--
Ron Savage, ro...@de... on 6/11/2003. Room EF 312
Deakin University, 221 Burwood Highway, Burwood, VIC 3125, Australia
Phone: +61-3-9251 7067, Fax: +61-3-9251 7604
http://www.deakin.edu.au/~rons
|
|
From: Michael G S. <sc...@po...> - 2003-11-06 04:50:47
|
On Thu, Nov 06, 2003 at 02:53:53PM +1100, Ron Savage wrote: > I'm trying to replace my module Module::MakeDist with Module::Build, > and have a problem with 'Build dist'. > > Build.PL: > -----><8----- > use Module::Build; > > Module::Build -> new > ( > code_base => './x86/CGI-Explorer-2.02.tar.gz', What's code_base? -- Michael G Schwern sc...@po... http://www.pobox.com/~schwern/ I knew right away that my sock and your eyebrows could be best friends. |
|
From: Randy W. S. <Ra...@Th...> - 2003-11-06 05:38:43
|
On 11/5/2003 11:50 PM, Michael G Schwern wrote: > On Thu, Nov 06, 2003 at 02:53:53PM +1100, Ron Savage wrote: > >>I'm trying to replace my module Module::MakeDist with Module::Build, >>and have a problem with 'Build dist'. >> >>Build.PL: >>-----><8----- >>use Module::Build; >> >>Module::Build -> new >>( >> code_base => './x86/CGI-Explorer-2.02.tar.gz', > > > What's code_base? > > 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" For the errors, try updating your version of Archive::Tar from: <http://p4.elixus.org/snap/Archive-Tar.tar.gz> until 1.08 is released. Randy. |
|
From: Dave R. <au...@ur...> - 2003-11-06 05:45:04
|
On Thu, 6 Nov 2003, Randy W. Sims wrote: > > 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" I just want to point out that I wrote the PPD related code for M::B, and I'd encourage someone who understands PPM/PPD stuff better than I to go through and improve, since I'm sure it's got problems ;) -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/ |
|
From: Ron S. <ro...@de...> - 2003-11-06 06:17:00
|
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=3D"./x86/CGI-Explorer-2.02.tar.gz"
OK.
The output is:
-----><8-----
<IMPLEMENTATION>
<CODEBASE HREF=3D"./x86/CGI-Explorer-2.02.tar.gz" />
</IMPLEMENTATION>
-----><8-----
whereas it should look like (this is downloaded from Randy Kobe's
site):
-----><8-----
=09<IMPLEMENTATION>
=09=09<OS NAME=3D"MSWin32" />
=09=09<ARCHITECTURE NAME=3D"MSWin32-x86-multi-thread-5.8" />
=09=09<CODEBASE
HREF=3D"http://theoryx5.uwinnipeg.ca/ppms/x86/Module-Build.tar.gz" />
=09</IMPLEMENTATION>
-----><8-----
> 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:
-----><8-----
C:\perl-modules\CGI-Explorer-2.02>perl Build dist
Deleting META.yml
mkdir CGI-Explorer-2.02
mkdir CGI-Explorer-2.02/images
mkdir CGI-Explorer-2.02/examples
mkdir CGI-Explorer-2.02/css
mkdir CGI-Explorer-2.02/t
mkdir CGI-Explorer-2.02/lib
mkdir CGI-Explorer-2.02/lib/CGI
mkdir CGI-Explorer-2.02/js
Creating CGI-Explorer-2.02.tar.gz
Deleting CGI-Explorer-2.02
-----><8-----
But CGI-Explorer-2.02.tar.gz does not contain any paths :-(.
--
Ron Savage, ro...@de... on 6/11/2003. Room EF 312
Deakin University, 221 Burwood Highway, Burwood, VIC 3125, Australia
Phone: +61-3-9251 7067, Fax: +61-3-9251 7604
http://www.deakin.edu.au/~rons
|
|
From: Randy W. S. <Ra...@Th...> - 2003-11-06 21:11:33
|
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. -- 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 |
|
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 |
|
From: Ron S. <ro...@de...> - 2003-11-07 01:30:32
|
On Thu, 06 Nov 2003 18:09:00 -0500, Randy W. Sims wrote: Hi Randy I'm subscribed to the list, so no need to copy me too. >> Does ppm >> fail without those tags? No, it's OK. > 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. Hmmm. Good guess but ... I'm using both WinZip and GNU gzip/tar for DOS. See: http://savage.net.au/Ron/html/GNU-Utils.html The GNU files I have are datestamped 1994 but it's only recently that they seem to be struggling. And all problems are only in this Archive::* context. When run by themselves (tar, gzip) everything is fine. I'd better upgrade Compress::ZLib now too. Anyway, WinZip and GNU agree that the files have no paths, so if you can see paths and I can't there is definitely a problem and it's definitely somewhere! Recall my very first statement in this thread that I was trying to replace my module Module::MakeDist. That's because I'm having these sorts of trouble with it, and it calls tar and gzip. I have these problems, but worse, at home under Win2K, and all such problems are very recent. Same GNU stuff at home of course. I'll investigate the port you mentioned, too. > As far as the ppd output, Dave's implementation is correct I accept that. -- Ron Savage, ro...@de... on 7/11/2003. Room EF 312 Deakin University, 221 Burwood Highway, Burwood, VIC 3125, Australia Phone: +61-3-9251 7067, Fax: +61-3-9251 7604 http://www.deakin.edu.au/~rons |
|
From: Randy W. S. <Ra...@Th...> - 2003-11-07 02:44:37
|
On 11/6/2003 8:30 PM, Ron Savage wrote: > Hmmm. Good guess but ... I'm using both WinZip and GNU gzip/tar for > DOS. See: > http://savage.net.au/Ron/html/GNU-Utils.html > The GNU files I have are datestamped 1994 but it's only recently that > they seem to be struggling. And all problems are only in this > Archive::* context. When run by themselves (tar, gzip) everything is > fine. I'd better upgrade Compress::ZLib now too. > > Anyway, WinZip and GNU agree that the files have no paths, so if you > can see paths and I can't there is definitely a problem and it's > definitely somewhere! > I've traced through M::B and A::Tar; the path information is definately being written to the tar file, but there must be some disagreement between these programs on the tar file spec. What happens if you run: ptar xvzf file.tar.gz Randy. |
Thanks for helping keep SourceForge clean.
X