Re: [perl #50010] [BUG]: make failure: conflicting types for 'Parrot_set_executable_name'

2008-01-20 Thread Matisse Enzer
and Darwin. Thanks. Is there someone with a Darwin box who is willing to run a buildbot build slave on it? If so, please let me know and I'll add it to my build master at http://buildbot.eigenstate.net:8040/ -M --- Matisse Enzer [EMAIL PROTECTED

Re: ubuntu-ppc-trunk BUILD FAILED

2008-01-14 Thread Matisse Enzer
would like to another build slave please let me know. The more the merrier. -M --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: ubuntu-ppc-trunk BUILD FAILED

2008-01-14 Thread Matisse Enzer
?parrot OK - done. I have edited http://www.perlfoundation.org/parrot/index.cgi?parrot and added a new page http://www.perlfoundation.org/parrot/index.cgi?buildbot -M --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http

Re: ubuntu-ppc-trunk BUILD FAILED

2008-01-13 Thread Matisse Enzer
(yet.) /msg eigenbot status to watch a currently running build (get builder names from 'status'): /msg eigenbot watch {builder-name} On Jan 13, 2008, at 9:33 AM, Andy Armstrong wrote: On 13 Jan 2008, at 17:28, Matisse Enzer wrote: Yup, I saw that. Would it help if I set up a mailing

Re: ubuntu-ppc-trunk BUILD FAILED

2008-01-12 Thread Matisse Enzer
. --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: ubuntu-ppc-trunk BUILD FAILED

2008-01-12 Thread Matisse Enzer
have a suitable server. For now I just want to see if people are interested and find the tool useful. What would it take to create a separate perl.org mailing list for buildbot status messages? -M --- Matisse Enzer [EMAIL PROTECTED] http

Re: ubuntu-ppc-trunk BUILD FAILED

2008-01-12 Thread Matisse Enzer
. --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: Gearing up for Parrot release 0.5.2

2008-01-12 Thread Matisse Enzer
On Jan 12, 2008, at 8:29 PM, Andy Lester wrote: We need to be talking more about what we're doing. Consider the outside person who's only vaguely, if at all, familiar with Parrot. pbc_to_exe means nothing to them. ++ --- Matisse

continuous integration server (buildbot) for parrot?

2008-01-11 Thread Matisse Enzer
#Installing_and_Configuring_BuildBot --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: [perl #49408] AutoReply: parrot make test Failed test (t/stm/basic_mt.t at line 93)

2008-01-05 Thread Matisse Enzer
More info: Test failed on SVN revision 24566, but passed in revision 24567 So OK to close this one.

Re: Changing permissions on temporary directories during testing

2006-05-21 Thread Matisse Enzer
On May 21, 2006, at 7:29 PM, James E Keenan wrote: Let's say that I'm writing a test suite for a Perl module which creates files and then, optionally, moves those files to predetermined directories. To test this module's functionality, I would have to see what happens when the user

Re: [OT] TDD + Pair Programming

2006-04-01 Thread Matisse Enzer
the test pass. Each mini-iteration might take between 1 and 5 minutes. Here's a pretty good Power Point slide show that demonstrates the process: http://www.butunclebob.com/files/downloads/Bowling%20Game%20Kata.ppt --- Matisse Enzer [EMAIL

Re: Module requirements (was: Module::Build and installing in non-standardlocations)

2006-04-01 Thread Matisse Enzer
On Mar 31, 2006, at 11:02 AM, Adam Kennedy wrote: Most end users don't see the build stage as being somehow distinct, all they want to do is install a module. I agree 100% with that, and urge others to keep that in mind. --- Matisse

Re: Module::Build and installing in non-standard locations

2006-03-30 Thread Matisse Enzer
On Tue, 28 Mar 2006, Randy W. Sims wrote: There are a number of ways to do this. The most simple is: use strict; use warnings; use File::HomeDir; my $conf_dir = File::Spec-catdir( File::HomeDir-my_home, '.Foo' ); use Module::Build; my $builder = Module::Build-new( module_name

Re: Module::Build and installing in non-standard locations

2006-03-30 Thread Matisse Enzer
On Thu, 30 Mar 2006, Randy W. Sims wrote: Note that the entries in install_path must have the same name as supplied to add_build_element() (not with the '_files' appendage). OK - thanks again, that is my problem... the naming of the entries... I was too dense to appreciate your note about the

Module::Build and installing in non-standard locations

2006-03-28 Thread Matisse Enzer
What's the standard (if any) for how to configure a build script to install specific files (e.g. httpd.conf) in someplace other than the standard Perl library/script/man locations? For example, if my distro contains a bunch of .pm files and .pl files, which go in the normal place, and my

Re: Module::Build and installing in non-standard locations

2006-03-28 Thread Matisse Enzer
On Tue, 28 Mar 2006, Randy W. Sims wrote: The add_build_element() method is the key to the process. Ah-Ha and thank you Very Nice! I did read the perldoc - but just didn't get that add_build_element('foo_files') would make M::B look for a foo_fiels element - and I thought i would have to

Re: Best practice for version control of locally installed CPAN modules

2006-03-06 Thread Matisse Enzer
On Mar 6, 2006, at 4:10 AM, Nik Clayton wrote: Matisse Enzer wrote: Currently we are evaluating these options: 1) Maintain a list of the .tar.gz files and install from CPAN, for example M/MA/MATISSE/Text-TagTemplate-1.8.tar.gz 2) Put the CPAN .tar.gz files in a local CPAN repository

Re: ANNOUNCE - Smolder 0.01

2006-03-05 Thread Matisse Enzer
After some trouble, I managed to create a distribution tarball for my patched Redhat 8 system from smolder-0.01-src using bin/ smolder_makedist. The problem I encountered was in src/libapreq-1.3.tar.gz - specifically in src/libapreq-1.3/Makefile.PL (after unpacking the tarball) the

Re: ANNOUNCE - Smolder 0.01

2006-03-05 Thread Matisse Enzer
On Mar 5, 2006, at 3:15 PM, Michael Peters wrote: Matisse Enzer wrote: After some trouble, I managed to create a distribution tarball for my patched Redhat 8 system from smolder-0.01-src using bin/ smolder_makedist. Thanks for trying this out so soon. It's been developed on FC3

Re: Best practice for version control of locally installed CPAN modules

2006-03-02 Thread Matisse Enzer
I did some experimenting yesterday with CPAN::Mini::Inject and our Subversion repository: As many of you know, in the Subversion source control system every file has a URL - it can be a file:// url, an http:// URL, an svn:// URL, etc. I think what will work well for us is to use

Re: Trends in Code Quality

2006-03-02 Thread Matisse Enzer
) things for me - I *feel better* doing TDD, it is actually easier for me in most cases, as well as faster (for me) and more accurate - I write better code. Of course, Your Milage May Vary (YMMV) --- Matisse Enzer [EMAIL PROTECTED] http

Re: Trends in Code Quality

2006-03-02 Thread Matisse Enzer
the different environments - small company, large company, fast-moving, slow-moving, etc. --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: Best practice for version control of locally installed CPAN modules

2006-02-28 Thread Matisse Enzer
and Im glad to know about it. Thank you! -- Matisse Enzer [EMAIL PROTECTED] http://www.eigenstate.net/ - http://www.matisse.net/

Re: Best practice for version control of locally installed CPAN modules

2006-02-28 Thread Matisse Enzer
://search.cpan.org/~ssoriche/CPAN-Mini-Inject-.18/lib/CPAN/Mini/Inject.pm Yes thank you - I'm installing both to test. -- Matisse Enzer [EMAIL PROTECTED] http://www.eigenstate.net/ - http://www.matisse.net/

Best practice for version control of locally installed CPAN modules

2006-02-27 Thread Matisse Enzer
I'm helping plan inmprovements to a build deploy system and am wondering what people think is the best practice for handling version control of locally-installed CPAN modules. We have a bunch of code in version control (CVS now, moving to SVN soon) We also have a large number of CPAN modules

Re: Best practice for version control of locally installed CPAN modules

2006-02-27 Thread Matisse Enzer
complicated :-) I'll read it tomorrow when I've had some sleep. --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: Best practice for version control of locally installed CPAN modules

2006-02-27 Thread Matisse Enzer
(which could be multiple machines.) --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: Network Testing

2006-02-20 Thread Matisse Enzer
--- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: Request for Comments: Package testing results analysis, result codes

2006-02-20 Thread Matisse Enzer
one to specify the installed permissions of files, for example, if i want my executables to be installed as 550, or 4555 it doesn't look like I can do that. I could be wrong about that though. --- Matisse Enzer [EMAIL PROTECTED] http

Re: Test Script Best-Practices

2006-01-28 Thread Matisse Enzer
On Jan 27, 2006, at 6:06 PM, James E Keenan wrote: Steffen Schwigon wrote: Quite often -l (to read from lib/) is enough, depending on your module build complexity. For -b you have to call ./Build before prove, which can be annoying and/or difficult to remember. I'll have to try that out.

Re: How to best have statements execute only during dev/testing?

2006-01-11 Thread Matisse Enzer
On Jan 10, 2006, at 8:36 AM, dakkar wrote: This entry in BooK's use.perl journal might help you: http://use.perl.org/~BooK/journal/25445 Thanks - that is a helpful idea. --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http

Re: How to best have statements execute only during dev/testing?

2006-01-11 Thread Matisse Enzer
practical techniques, so we will have a couple good ideas to choose from rather than invent our own. --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

How to best have statements execute only during dev/testing?

2006-01-10 Thread Matisse Enzer
that Carp::Assert handles this issue by having you make all the test calls conditional: ASSERT( $a == $b) if DEBUG; -M --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: How to best have statements execute only during dev/testing?

2006-01-10 Thread Matisse Enzer
By the way - I have also been looking at Test::Assertions --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: How to best have statements execute only during dev/testing?

2006-01-10 Thread Matisse Enzer
. --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: What about Test::Unit?

2006-01-09 Thread Matisse Enzer
again, Matisse --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

What about Test::Unit?

2006-01-08 Thread Matisse Enzer
Test::Unit is at: http://twoalpha.blogspot.com/2005/11/unit-testing-in-perl-with- testunit.html --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Parsing perl without Perl (sort of)

2005-06-10 Thread J Matisse Enzer
on Perl 6 design? --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/ 415-225-6703 (work/cellphone) 415-401-8325 (home)

Re: Perl6 and support for Refactoring IDE's

2005-06-03 Thread J Matisse Enzer
Eclipse are for another language it really has made me see how far behind Perl is in this area. I'm really scared that Perl will be an unacceptable choice for larger projects in less than a two years. -Matisse --- Matisse Enzer [EMAIL PROTECTED

Perl6 and support for Refactoring IDE's

2005-05-06 Thread J Matisse Enzer
to support extract subroutine, but a lot more is needed to match what you can do with Java these days. What are others' thoughts on this? --- Matisse Enzer [EMAIL PROTECTED] http://www.matisse.net/ - http://www.eigenstate.net/

Re: Perl6 and support for Refactoring IDE's

2005-05-06 Thread J Matisse Enzer
this, so I'll take pointers to other places. I'm very worried about the continued viability of Perl for major projects and am trying connect with other people and see what can be done about it. --- Matisse Enzer [EMAIL PROTECTED] http