module-build-general Mailing List for Module::Build (Page 150)
Status: Beta
Brought to you by:
kwilliams
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(24) |
Sep
(2) |
Oct
(18) |
Nov
(36) |
Dec
(17) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(3) |
Feb
(96) |
Mar
(82) |
Apr
(63) |
May
(90) |
Jun
(52) |
Jul
(94) |
Aug
(89) |
Sep
(75) |
Oct
(118) |
Nov
(101) |
Dec
(111) |
| 2004 |
Jan
(159) |
Feb
(155) |
Mar
(65) |
Apr
(121) |
May
(62) |
Jun
(68) |
Jul
(54) |
Aug
(45) |
Sep
(78) |
Oct
(80) |
Nov
(271) |
Dec
(205) |
| 2005 |
Jan
(128) |
Feb
(96) |
Mar
(83) |
Apr
(113) |
May
(46) |
Jun
(120) |
Jul
(146) |
Aug
(47) |
Sep
(93) |
Oct
(118) |
Nov
(116) |
Dec
(60) |
| 2006 |
Jan
(130) |
Feb
(330) |
Mar
(228) |
Apr
(203) |
May
(97) |
Jun
(15) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Randy W. S. <Ra...@Th...> - 2003-11-10 22:20:34
|
Terrence Brannon wrote: > Thanks for all the work to get Module::Build functional under Cygwin. I > was not able to run the more-recent versions of Alzabo until this > happened. However, attempting to install Alzabo-0.80 yields an error > which appears to be coming from Module::Build. I just installed Cygwin 3 > days ago, so it is definitely the latest version. > It will be at least tomorrow before I can try this out under Cygwin. What happens if you build/test this manually with verbose=1? Randy. |
|
From: Terrence B. <met...@ur...> - 2003-11-10 12:32:03
|
Thanks for all the work to get Module::Build functional under Cygwin. I
was not able to run the more-recent versions of Alzabo until this
happened. However, attempting to install Alzabo-0.80 yields an error
which appears to be coming from Module::Build. I just installed Cygwin 3
days ago, so it is definitely the latest version.
Some of the CPAN.pm output is removed to facilitate reading.
The Perl version is 5.8.0
Module::Build is 0.21
~ $ perl -MCPAN -e 'install Alzabo'
CPAN: Storable loaded ok
Going to read /home/metaperl/.cpan/Metadata
Database was generated on Mon, 10 Nov 2003 07:50:25 GMT
Running install for module Alzabo
Running make for D/DR/DROLSKY/Alzabo-0.80.tar.gz
CPAN: Digest::MD5 loaded ok
CPAN: Compress::Zlib loaded ok
Checksum for
/home/metaperl/.cpan/sources/authors/id/D/DR/DROLSKY/Alzabo-0.80.tar.gz ok
Scanning cache /home/metaperl/.cpan/build for sizes
Deleting from cache: /home/metaperl/.cpan/build/Alzabo-0.80 (10.5>10.0 MB)
Alzabo-0.80/
Alzabo-0.80/t/
Alzabo-0.80/t/05a-rules-mysql.t
Alzabo-0.80/t/02-create.t
...
Alzabo-0.80/INSTALL
Alzabo-0.80/Makefile.PL
Alzabo-0.80/SIGNATURE
CPAN.pm: Going to build D/DR/DROLSKY/Alzabo-0.80.tar.gz
/usr/bin/perl Build.PL
Please select a root directory for Alzabo (schema files will be stored
under this root.
Alzabo root? [/home/metaperl/alzaobo] /home/metaperl/alzabo
The following questions pertain to optional features of Alzabo. These
questions help the installer determine what additional system checks
to perform.
To use the MySQL driver requires DBD::mysql (2.1017).
Do you want to use the MySQL driver? [no]
no
To use the PostgreSQL driver requires DBD::Pg (1.13).
Do you want to use the PostgreSQL driver? [yes]
yes
The information from the following questions are used solely for
testing the pieces of Alzabo that require a real database for proper
testing.
Do tests with Postgres RDBMS? [yes]
yes
Please provide a username that can be used to connect to the Postgres
RDBMS? This user must have the ability to create a new
database/schema.
Username? metaperl
Password for metaperl?
What host is the Postgres RDBMS located on. Press enter to skip this if
the database server is located on the localhost or can be determined
in another way (for example, Oracle can use TNS to find the database).
Host?
What port is the Postgres RDBMS located on. Press enter to skip this.
Port?
Please provide a database name that can be used for testing. A
database/schema with this name will be created and dropped during the
testing process.
Database name? [test_alzabo_pg]
test_alzabo_pg
Usage: Cwd::cwd() at /usr/lib/perl5/site_perl/5.8.0/Module/Build/Base.pm
line 84.
Couldn't run Build.PL: at
/usr/lib/perl5/site_perl/5.8.0/Module/Build/Compat.pm line 120.
Running make test
Make had some problems, maybe interrupted? Won't test
Running make install
Make had some problems, maybe interrupted? Won't install
~ $
|
|
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. |
|
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-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: 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: 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: 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: 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: 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: 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: Steve P. <sp...@qu...> - 2003-11-04 21:28:56
|
On Monday, November 3, 2003, at 05:00 pm, Randy W. Sims wrote: > Ken Williams wrote: >> Hi all, >> I'm getting married at the end of this week and then I'm going to >> Belgium on a honeymoon for 10 days. I also started a new full-time >> job 3 weeks ago so I can't hang out in the coffee shop all day and >> goof off with open source stuff. =) >> Just wanted to let people know I'll be back, and that if it looks >> like I've dropped off the face of the earth I actually haven't. >> -Ken > > Congratulations! I wish you both well in your new life together, and > you in your new job. Yeah - congrats Ken! Hope you have a good wedding, and well, Belgium - you're sure to have a good honeymoon there! If you don't have an itinerary planned already I've heard Bruges is quite nice... -Steve |
|
From: Yitzchak Scott-T. <sth...@ef...> - 2003-11-04 03:02:23
|
On Mon, Nov 03, 2003 at 10:32:09AM -0600, Ken Williams <ke...@ma...> wrote: > Hi all, > > I'm getting married at the end of this week and then I'm going to > Belgium on a honeymoon for 10 days. I also started a new full-time job > 3 weeks ago so I can't hang out in the coffee shop all day and goof off > with open source stuff. =) > > Just wanted to let people know I'll be back, and that if it looks like > I've dropped off the face of the earth I actually haven't. Is it okay to integrate Module::Build into the core and generate a few hundred bug reports while you are away? I'm not actually joking...as I understand it, Hugo's plan was to release 5.9.0 as a kind of baseline and then start work toward 5.9.1 by adding Module::Build, CPANPLUS, etc. and see what smoke comes up. 5.9.0 was released a week ago, but I haven't seen anything progressing since (other than 5.8.2). |
|
From: Randy W. S. <Ra...@Th...> - 2003-11-03 17:00:26
|
Ken Williams wrote: > Hi all, > > I'm getting married at the end of this week and then I'm going to > Belgium on a honeymoon for 10 days. I also started a new full-time job > 3 weeks ago so I can't hang out in the coffee shop all day and goof off > with open source stuff. =) > > Just wanted to let people know I'll be back, and that if it looks like > I've dropped off the face of the earth I actually haven't. > > -Ken > Congratulations! I wish you both well in your new life together, and you in your new job. I guess the open source community will have to patiently await your return. ;) Regards, Randy. |
|
From: Ken W. <ke...@ma...> - 2003-11-03 16:32:17
|
Hi all, I'm getting married at the end of this week and then I'm going to Belgium on a honeymoon for 10 days. I also started a new full-time job 3 weeks ago so I can't hang out in the coffee shop all day and goof off with open source stuff. =) Just wanted to let people know I'll be back, and that if it looks like I've dropped off the face of the earth I actually haven't. -Ken |
|
From: Randy W. S. <Ra...@Th...> - 2003-11-02 19:58:38
|
I just realized that I forgot the most important thing in that piece of a patch I posted--attributing MakeMakers authors. The code and most of the comments in the function _find_static_perl_libs() came from MakeMaker (EU::MM_Unix::makeaperl()) though it's changed due to adapting it to M::B, changing use of regexs to File::Spec functions for modifying paths, and general hacking. Regards, Randy. |
|
From: Randy W. S. <Ra...@Th...> - 2003-11-02 18:55:11
|
On 10/30/2003 9:36 PM, Randy W. Sims wrote: > Hi Ken, > > Version 1.220 of M::B::Base.pm uncovered a bug. On Windows, an > executable requires different options to the linker than a dynamic > library. Currently link_c() is configured strictly to produce libraries. > A quick and perhaps naive fix is to introduce an optional paramater to > link_c() to indicate the desired type of the output file. But, I want to > wait as I've also been looking into porting to AT&T's U/WIN Unix on > Windows environment <http://www.research.att.com/sw/tools/uwin/> (like > Cygwin, and it is going to require implementing static linking (see > "Static Linking of a new Perl Binary" in the MM docs). This might also > involve changes to link_c(), but I'm not sure yet. I'll post more when I > learn more and before I start patching. But it may be this weekend as > I'm going to set up a new computer thats been collecting dust; I'm going > to setup Debain linux, one of the BSDs, Windows 2000, & Windows 98, > multiboot so that I'll have a good testing system. > > Regards, > Randy. > I didn't get to work on this as much as I had hoped, but I did get some of the scaffolding in place for the static linking. I've attached it in case you want to look it over to see where it's going. It may be toward the middle of the week before I can get back to it. Regards, Randy. |
|
From: Sagar S. <sag...@so...> - 2003-11-01 13:54:17
|
Hi, I found the create_readme feature by searching the mailing lists ( i was just about to submit an enhancement for it)=20 I don't see it in the docs of Module::Build 0.21, but i do see it in the code. Since the original mail trail was back in september i decided to assume it was complete and gave it a go. One problem that i've found is that when generating the MANIFEST Module::Build doesn't add the README to it, and so it doesn't actually get includede in the dist tarball... Bug? Regards Sagar --=20 Sagar Shah <sag...@so...> |
|
From: Sagar S. <sag...@so...> - 2003-11-01 13:30:30
|
Hi, First of all thank you for producing Module::Build. Even at this stage of development, it is excellent. I like the idea of the recommends method, as i often have optional dependencies for my modules (mainly things that are dependencies of specific tests which get skipped when the module isn't there). I had a quick play with it, and what i'm not sure is whether it's friendly enough to the user. If i have an uninstalled module 'Sagar::Great' =3D> 1, in requires iget the following output: ERROR: Sagar::Great: Prerequisite Sagar::Great isn't installed ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation. Which sounds fairly reasonable. Now if i have an uninstalled module: 'Sagar::SICRAP' =3D> 3, i get: WARNING: Sagar::Great: Prerequisite Sagar::Great isn't installed ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation. My concern is that the 'ERRORS/WARNINGS FOUND..." message is a bit too harsh/unfriendly when all that the user is missing is a recommended module. It puts me off using the recommends feature. What do others think? Perhaps something more akin to : WARNING: Sagar::Great: Optional Sagar::Great isn't installed You may wish to install the recommended versions of the modules indicated above before proceeding with this installation. Or perhaps i'm just too nice to my users ;-) S. --=20 Sagar Shah <sag...@so...> |
|
From: Randy W. S. <Ra...@Th...> - 2003-10-31 02:36:47
|
Hi Ken, Version 1.220 of M::B::Base.pm uncovered a bug. On Windows, an executable requires different options to the linker than a dynamic library. Currently link_c() is configured strictly to produce libraries. A quick and perhaps naive fix is to introduce an optional paramater to link_c() to indicate the desired type of the output file. But, I want to wait as I've also been looking into porting to AT&T's U/WIN Unix on Windows environment <http://www.research.att.com/sw/tools/uwin/> (like Cygwin, and it is going to require implementing static linking (see "Static Linking of a new Perl Binary" in the MM docs). This might also involve changes to link_c(), but I'm not sure yet. I'll post more when I learn more and before I start patching. But it may be this weekend as I'm going to set up a new computer thats been collecting dust; I'm going to setup Debain linux, one of the BSDs, Windows 2000, & Windows 98, multiboot so that I'll have a good testing system. Regards, Randy. |
|
From: Randy W. S. <Ra...@Th...> - 2003-10-31 02:22:06
|
On 10/30/2003 2:35 AM, Andrew Savige wrote: > A snapshot of the latest development version of Archive::Tar may > always be got from: http://p4.elixus.org/snap/Archive-Tar.tar.gz. > I believe this snapshot is now finally quite solid on Windows; > I tested it with M::B 0.21 and did not notice any spurious A::T > warning messages. If you notice any problems with this snapshot > during your M::B testing, please let me know. > > /-\ (hoping A::T 1.08 is released before M::B 0.22 :-) > Yeah, this tests clean with the current CVS on Windoze. This also seems to fix a few other problems I had run into in a script I wrote the other day. Thanks. |
|
From: <ajs...@ya...> - 2003-10-30 07:35:56
|
A snapshot of the latest development version of Archive::Tar may always be got from: http://p4.elixus.org/snap/Archive-Tar.tar.gz. I believe this snapshot is now finally quite solid on Windows; I tested it with M::B 0.21 and did not notice any spurious A::T warning messages. If you notice any problems with this snapshot during your M::B testing, please let me know. /-\ (hoping A::T 1.08 is released before M::B 0.22 :-) http://personals.yahoo.com.au - Yahoo! Personals New people, new possibilities. FREE for a limited time. |
|
From: Ken W. <ke...@ma...> - 2003-10-28 03:27:35
|
On Wednesday, October 22, 2003, at 08:15 PM, Randy W. Sims wrote:
>
>
> On 10/15/2003 11:08 PM, Randy W. Sims wrote:
>
>> On 10/15/2003 8:46 AM, Ken Williams wrote:
>>>
>>>> BTW, wouldn't it be better to use Pod::Parser in the dist_*
>>>> routines for more acurate results?
>>>
>>>
>>>
>>> Probably so, yeah. Is that a core module?
>>>
>>> -Ken
>> Yeah, though I'm not sure when it was added. The attached patch
>> should be safe though.
>> Randy.
>
> I forgot to follow up on this. I also forgot how easy it is to find
> out when a module was added to CORE with Module::CoreList:
>
> $ perl -MModule::CoreList -e "print
> Module::CoreList->first_release('Pod::Parser')"
> 5.006
>
> Even though it's kind of new, I'd recommend using it if it's present
> since the current method is flawed.
Okay, I've committed a patch that uses Pod::Parser if available. I
based it on your code, but moved it out into a new
Module::Build::PodParser module that can transmogrify itself based on
whether Pod::Parser is available.
-Ken
|
|
From: Chris D. <ch...@cl...> - 2003-10-24 11:00:18
|
I have 19 M::B-based Perl packages (and at least 7 Flash packages) that I hope to include soon! As soon as we can get the last few license and package details worked out... Chris On Wednesday, October 22, 2003, at 08:09 PM, Randy W. Sims wrote: > I was curious to see what modules where using M::B, and I also thought > having a list of those module might be useful. I used Randal > Schwartz's minicpan script to update my local archive with just the > most recent versions of each module from CPAN. I then wrote a little > script to peek inside each of those modules and generate the attached > report. > > The first field in the report (which is empty in this edition) would > have an XS if any XS modules where present. The second field is the > CPAN author ID for the module author, and the third field is the > module name-version. > > Randy. > > $ build_stats 2>nul > > XS AuthID Module > == ========== ============================================== > ABERGMAN Alien-0.91 > ABERGMAN B-Generate-1.06 > ABERGMAN File-Find-Random-0.5 > ABERGMAN optimize-0.03 > ABERGMAN types-0.05 > ASAVIGE Acme-EyeDrops-1.43 > AUTRIJUS Acme-Hello-0.02 > AUTRIJUS WWW-SherlockSearch-0.15 > AUTRIJUS XML-RSS-Aggregate-0.02 > BDFOY Test-Prereq-0.19 > BDULFER CPANPLUS-Shell-Tk-0.02 > BROQ Filter-Include-1.3 > BROQ Module-Locate-1 > CHROMATIC Acme-Incorporated-0.10 > CHROMATIC Mail-SimpleList-0.81 > CHROMATIC Text-WikiFormat-0.71 > CWEST Class-DBI-SAK-1.4 > CWEST Devel-Caller-Perl-1.4 > CWEST Parse-PhoneNumber-1.1 > CWEST poest-0.20030407 > DAVECROSS Array-Compare-1.09 > DAVECROSS AudioFile-Info-1.02 > DAVECROSS AudioFile-Info-1.05 > DAVECROSS AudioFile-Info-MP3-ID3Lib-1.02 > DAVECROSS AudioFile-Info-MP3-Info-1.01 > DAVECROSS AudioFile-Info-Ogg-Vorbis-Header-1.03 > DAVECROSS AudioFile-Info-Ogg-Vorbis-Header-PurePerl-1.02 > DAVECROSS Template-Plugin-AudioFile-Info-0.01 > DOMM Module-CPANTS-0.20030913 > DROLSKY Alzabo-0.73 > DROLSKY Alzabo-GUI-Mason-0.09 > DROLSKY Class-AlzaboWrapper-0.01 > DROLSKY DateTime-Format-ICal-0.08 > DROLSKY DateTime-Format-MySQL-0.03 > DROLSKY DateTime-Locale-0.05 > DROLSKY DateTime-TimeZone-0.2503 > DROLSKY Log-Dispatch-2.07 > DROLSKY Thesaurus-0.21 > DWHEELER Apache-FakeTable-0.02 > DWHEELER App-Info-0.24 > DWHEELER Bundle-Bricolage-1.6.1 > DWHEELER Bundle-BricolagePlus-1.6.1 > DWHEELER Data-Types-0.05 > DWHEELER Exception-Class-DBI-0.91 > DWHEELER Lingua-Strfname-0.10 > DWHEELER Params-CallbackRequest-1.11 > DWHEELER Time-Piece-ISO-0.05 > EMARTIN Acme-Lingua-Pirate-Perl-0.12 > EMARTIN WWW-Lipsum-0.11 > FLORIAN Finance-Bank-Bundesschatz-1.01 > FLUFFY Class-MethodMaker-1.12 > FLUFFY Term-ProgressBar-2.05 > HUANGWEI Class-Builder-1.010 > JCROMIE Log-Log4perl-AutoCategorize-0.02 > JFORGET DateTime-Calendar-FrenchRevolutionary-0.04 > JHOBLITT DateTime-Calendar-Mayan-0.06 > JHOBLITT DateTime-Format-Bork-0.02 > JHOBLITT DateTime-Format-ISO8601-0.03 > JHOBLITT DateTime-HiRes-0.01 > JHOBLITT DateTime-TimeZone-Alias-0.05 > JSHY DateTime-Fiscal-Year-0.02 > JSMITH Gestinanna-POF-0.04 > JSMITH Gestinanna-POF-Repository-0.01 > KAKE CGI-Wiki-Formatter-Multiple-0.01 > KAKE CGI-Wiki-Kwiki-0.43 > KAKE OpenGuides-0.26 > KWILLIAMS AI-Categorizer-0.06 > KWILLIAMS AI-Categorizer-0.07 > KWILLIAMS Algorithm-NaiveBayes-0.02 > KWILLIAMS Apache-Filter-1.022 > KWILLIAMS Class-Container-0.10 > KWILLIAMS Crypt-SKey-0.06 > KWILLIAMS File-Spec-0.86 > KWILLIAMS HTML-SimpleParse-0.12 > KWILLIAMS Module-Build-0.21 > KWILLIAMS Tie-TextDir-0.06 > LBROCARD Acme-Colour-1.00 > LBROCARD CPAN-Metadata-RDF-1.10 > LBROCARD CPAN-WWW-Testers-0.22 > LBROCARD CPAN-WWW-Testers-Generator-0.20 > LBROCARD Data-Page-0.18 > LBROCARD Image-Imlib2-1.00 > LBROCARD Module-CPANTS-Generator-0.006 > LBROCARD OpenFrame-Segment-Apache-1.10 > MARCEL String-FlexMatch-0.05 > MARKF Acme-VerySign-1.00 > MARKF Attempt-1.01 > MARKF File-Path-Stderr-1.00 > MARKF Template-Plugin-Clone-0.01 > MARKF Template-Plugin-ListUtil-0.02 > MARKF Template-Plugin-Textile-1.01 > MARKF Template-Plugin-VMethods-0.03 > MARKF Template-Plugin-XML-LibXML-1.06 > MARKSTOS CGI-Application-ValidateRM-1.07 > MARKSTOS Data-FormValidator-3.12 > MBARBON Wx-Perl-FSHandler-LWP-0.01 > MIROD Params-Style-0.02 > MOLT SDL-OpenGL-Cg-0.01 > NKUITSE Class-Proxy-Lite-1.00 > PMISON File-Find-Rule-Type-0.05 > PMISON File-Type-0.11 > PNE Lingua-Klingon-Collate-1.01 > PNE Lingua-Klingon-Segment-1.0 > PROFERO Template-Plugin-CaseVMethods-0.01 > PROFERO Test-CGI-Untaint-1.10 > RCAPUTO POE-0.27 > RCLAMP Acme-USIG-1.04 > RCLAMP Algorithm-GenerateSequence-0.02 > RCLAMP Class-DBI-BaseDSN-1.22 > RCLAMP Class-Delay-0.02 > RCLAMP Devel-Caller-0.09 > RCLAMP Devel-LeakTrace-0.05 > RCLAMP Devel-System-0.01 > RCLAMP Device-Ericsson-AccessoryMenu-0.7 > RCLAMP Email-Folder-0.8 > RCLAMP Email-FolderType-0.6 > RCLAMP Email-LocalDelivery-Ezmlm-0.10 > RCLAMP File-Find-Rule-0.25 > RCLAMP File-Find-Rule-CVS-0.01 > RCLAMP File-Path-Expand-1.01 > RCLAMP File-Slurp-Tree-1.22 > RCLAMP Games-Set-0.01 > RCLAMP Games-Tetris-0.01 > RCLAMP Mail-Thread-Chronological-1.22 > RCLAMP Mariachi-0.51 > RCLAMP Parse-CVSEntries-0.03 > RCLAMP Pod-Coverage-0.12 > RCLAMP Siesta-0.66 > RCLAMP Template-Plugin-Class-0.11 > RCLAMP Template-Plugin-YAML-1.22 > RCLAMP Text-Glob-0.06 > RMCKAY Finance-Bank-CreateCard-1.03 > SAPER Config-Natural-0.97 > SCHUMACK CircuitLayout-0.05 > SEMANTICO Class-DBI-ToSax-0.10 > SEMANTICO Test-XML-0.06 > SEMANTICO XML-Filter-Namespace-1.03 > SEMANTICO XML-SAX-Builder-0.02 > SIMON Apache-OneTimeURL-1.0 > SIMONW LWPx-TimedHTTP-1.2 > SIMONW Module-Pluggable-0.9 > SIMONW Python-Serialise-Marshal-0.02 > SIMONW Python-Serialise-Pickle-0.01 > SIMONW Template-Plugin-ShellQuote-1.3 > SIMONW Text-DeSupercite-0.6 > SPURKIS AI-Perceptron-1.0 > SPURKIS OpenFrame-WebApp-0.04 > SPURKIS Pangloss-0.05 > SPURKIS Petal-Utils-0.04 > SPURKIS Pipeline-Config-0.05 > SPURKIS accessors-0.02 > SRSHAH CGI-Widget-Tabs-1.08 > SRSHAH Template-Plugin-EnvHash-1.01 > STEFAN Alzabo-Display-SWF-0.01 > STRUAN WWW-Yahoo-Login-0.10 > TILLY Math-Fleximal-0.05 > TILLY ReleaseAction-0.05 > TILLY Tie-Static-0.03 > TOBEYA Nagios-Cmd-0.01 > TOMI AudioFile-Identify-MusicBrainz-0.23 > TOMI Bot-BasicBot-0.21 > TOMI CGI-Wiki-Formatter-Kwiki-0.02 > TSIBLEY XMMS-InfoPipe-0.031 > URI stem-0.10 > collate Unicode-Collate-Standard-V3_1_1-0.1 > dt-fmt-datemanip DateTime-Format-DateManip-0.01 > nameday DateTime-Event-NameDay-0.02 > > 167 occurences of 'Build.PL'. > 5914 files searched. -- Chris Dolan, Software Developer, Clotho Advanced Media Inc. 608-294-7900, 211 S Paterson Suite 260, Madison WI 53703 |
|
From: Randy W. S. <Ra...@Th...> - 2003-10-23 15:02:41
|
On 10/15/2003 11:08 PM, Randy W. Sims wrote:
> On 10/15/2003 8:46 AM, Ken Williams wrote:
>
>>
>>> BTW, wouldn't it be better to use Pod::Parser in the dist_* routines
>>> for more acurate results?
>>
>>
>>
>> Probably so, yeah. Is that a core module?
>>
>> -Ken
>
>
> Yeah, though I'm not sure when it was added. The attached patch should
> be safe though.
>
> Randy.
>
I forgot to follow up on this. I also forgot how easy it is to find out
when a module was added to CORE with Module::CoreList:
$ perl -MModule::CoreList -e "print
Module::CoreList->first_release('Pod::Parser')"
5.006
Even though it's kind of new, I'd recommend using it if it's present
since the current method is flawed.
Randy.
|