On Mar 7, 2011, at 10:40 AM, Alexandr Ciornii wrote:
Hello, David.
You really don't need Module::Build in build_requires. Because if you
don't have M::B, and Build.PL will be run, it will fail before any
CPAN client will be able to install M::B.
Well, one *might* need it if one were using
Builders,
For some time, I've been using this pattern in my Build.PL:
configure_requires = { 'Module::Build' = '0.30' },
create_makefile_pl = 'traditional',
build_requires = { 'Module::Build' = '0.30' },
However, while the build with Build.PL requires Module::Build, the build
On Nov 14, 2009, at 4:55 AM, David Golden wrote:
Module::Build 0.35_06 has arrived on CPAN. This closes all all
Critical, Important and Normal bug tickets from RT that are not
stalled for upstream fixes. I consider it RC0 for 0.36 and aim to
have it added to bleadperl for inclusion in the
On Nov 14, 2009, at 9:04 AM, David Golden wrote:
This one?
- Auto-detection of abstract and author fixed for mixed-case POD headers
(RT#51117) [David Wheeler]
If you want to send a patch for Changes to clarify... :-)
Or just send the literal text to me in an email -- a formal patch
On Sep 11, 2009, at 11:03 AM, Dave Rolsky wrote:
What do people think about changing M::B's default behavior to
generate all content (Makefile.PL, META.yml, README, LICENSE) in the
distdir generated directory rather than in the top source
directory?
+1
In theory, it sounds good. I do
On Sep 10, 2009, at 12:57 PM, David Golden wrote:
(1a) Should bundling modules into inc/ happen in $source or $distdir?
$distdir. The same should be true of MANIFEST, META.yml, and other
generated files, AFAIC.
(1b) For either choice in #1a, how should the behavior of “bundle_inc”
change
On Sep 7, 2009, at 8:39 AM, Nicholas Clark wrote:
Hey, look, another reason that M::I must die. ;-P
Is getting M::B bundling working anyone's itch?
You mean the M::I inc/ stuff?
David
On Sep 7, 2009, at 11:24 AM, Eric Wilhelm wrote:
https://svn.perl.org/modules/Module-Build/trunk/contrib/bundle.pl
What is missing is:
1) some interface to 1-step-setup the bundle,
2) detection/updating the bundled version before release,
3) testing
4) Documentation (most likely
On Sep 6, 2009, at 7:03 AM, David Golden wrote:
I think the CPAN Meta Spec
should be explicit on how how release status is determined (e.g.
whether _ in the version number string or parsed off a comment on
the $VERSION = line) and how it is communicated (e.g. tarball name
or field in the Meta
On Sep 4, 2009, at 6:07 AM, David Golden wrote:
I think we should try to make the overall Module::Build experience
pretty quiet by default and only spew process messages if --verbose is
true.
+1
David
On Aug 28, 2009, at 3:37 PM, David Golden wrote:
I know some people were looking into this but it turned out to be
fairly
easy. Needs live testing though.
Looks useful, thanks!
David
On Aug 19, 2009, at 8:33 AM, David Golden wrote:
New way: Default install paths are generated on demand based on
whatever
config values are in force and are not stored in the object.
Accessors for all
the install path properties now merge custom install paths in object
properties with the
On Jul 12, 2009, at 7:24 AM, Elliot Shank wrote:
Given the documentation for test_files(), the 0.34 behavior is
correct. I could invoke find_test_files() myself, but that isn't
public API. Is there a simple way of doing this?
I suggest submitting a patch that documents find_test_files().
On Jun 19, 2009, at 2:19 PM, David Golden wrote:
* Figure out if the bug still exists based on the code in the
repository trunk
http://svn.perl.org/modules/Module-Build/trunk/
* Update the ticket with your findings
I added a patch to show that this bug is indeed fixed:
On Jun 21, 2009, at 2:44 PM, David E. Wheeler wrote:
I added a patch to show that this bug is indeed fixed:
https://rt.cpan.org/Ticket/Display.html?id=24661
I also wrote a patch to address this issue:
https://rt.cpan.org/Ticket/Display.html?id=40177
And wrote a patch to document
On Jun 16, 2009, at 4:47 PM, Michael G Schwern wrote:
svn cp repo/trunk repo/tags/$taggit tag $tag -m 'Optional message'
You'll also want to push the tag back upstream. I do this:
git tag -a $tag
git push --tags
Best,
David
On Jun 10, 2009, at 8:14 PM, Ken Williams wrote:
Is anyone interested in switching the M::B repository from SVN to Git?
My own opinion probably doesn't matter much because I'm only a very
rare committer myself, but I wondered if some of the dual-life and
multiple-maintainer issues might be
Anyone familiar with [this issue](http://rt.cpan.org/Public/Bug/Display.html?id=43515
)?
Someone [checked in a workaround](http://github.com/SamuraiJack/module-build-jsan/commit/bb3842316052fdcf2240ca545f200b3745c724de
) for it in a fork of M::B::JSAN, so I'm trying to understand if
there's
On Apr 22, 2009, at 1:53 PM, Eric Wilhelm wrote:
# from Michael G Schwern
# on Wednesday 22 April 2009 13:38:
Class::Delegation went from 1.06 to 1.7.1. That's 1.60.0 to 1.7.1
Of course that's what it means. The fact you don't have to type the
last zero is just a convenience...
Of course.
On Apr 20, 2009, at 9:44 AM, Eric Wilhelm wrote:
Sure, you can't just treat a float as a tuple without fixing the width
of the second column. I imagine this is where everybody gets confused
and I think all we need to do is explain that.
Xconvert to vX
X.Y convert to vX.Y00
So for a while, I've been using
create_makefile_pl = 'passthrough',
In most of my modules. I get the impression that this is no longer
recommended, however. So what is?
Thanks,
David
On Apr 2, 2009, at 10:52 AM, Eric Wilhelm wrote:
What gives you that impression?
Just the odd comment dropped here and there.
The only thing *I* would recommend over passthrough is none. The
recent
CPANPLUS updates (thanks to David, Chris, and Jos) make it unnecessary
anyway.
I'm happy
On Apr 2, 2009, at 11:11 AM, David Golden wrote:
In most of my modules. I get the impression that this is no longer
recommended, however. So what is?
I use 'traditional' for anything that doesn't have dynamic
requirements (e.g. custom code in Build.PL). In those cases, I leave
out a
On Feb 2, 2009, at 9:51 AM, David Golden wrote:
(a) Have M::B or EU::MM/M::I create MYMETA.yml at the end of running
Build.PL or Makefile.PL -- this isn't an *author* issue, this is
something
that happens on end-user machines. If that file is created, then
other
toolchain modules or QA
On Feb 2, 2009, at 10:10 AM, Eric Wilhelm wrote:
Because I want to be able to build a PAR/exe/whatever for more than
one
platform from a single system. I could just jump through a bunch of
hoops trying to automate it with ssh, but I've done that already and
it
wasn't fun.
I think you
On Feb 1, 2009, at 12:35 PM, Eric Wilhelm wrote:
So, arbitrary code would check $^O eq 'MSWin32', or possibly something
silly like -d 'c:\\progra~1' and yield the desired answer on the
target environment. But, if I wanted to determine the win32
dependencies from Linux (for e.g. bundled
On Jan 27, 2009, at 3:57 PM, Michael G Schwern wrote:
A while ago, Audrey suggested inverting the process. Rather than
having a
program that spits out meta-data, have meta-data which might contain
programs.
You mean like Ant? Not sure about that…
Best,
David
On Dec 12, 2008, at 3:41 AM, Eric Wilhelm wrote:
I've just committed (svn r12149) David Wheeler's change to enable
check
subroutines on properties in Module::Build, which is now used to
validate the installdirs property.
Ah, great. Looks like you committed it as submitted, yes? Did you
On Nov 20, 2008, at 1:13 PM, Eric Wilhelm wrote:
I've reviewed the changes, logs, and bugs since the last release. It
looks like time to ship an alpha. I think the version.pm and tilde.t
fixes are sorely needed.
What about the parameters patch I sent a while ago? What happened to
that?
On Sep 29, 2008, at 09:31, David E. Wheeler wrote:
Eric, are you going to commit your patch so I can finish re-doing my
and resubmitting it?
Also, have we settled on 4- or 2- space indents yet? At this point,
though I prefer 4-space, I don't really care enough to press it, as
long
On Sep 28, 2008, at 08:25, David E. Wheeler wrote:
As for the rest of your patch David, would you mind porting it
forward to fit this refactor? I think the API you'll want is
basically like: _make_accessor($property, %opts).
Yes, I'll do that, but I'm less inclined to contribute
On Sep 28, 2008, at 01:23, Eric Wilhelm wrote:
Right. So that's part of why I like many small patches. Something
like that makes the test pass, but it usually points to a bigger
problem.
My patch was small. It did only two things:
* Add support for params to add_property()
* Add
Heya,
In what version of Module::Build was this issue fixed?
http://www.nntp.perl.org/group/perl.cpan.testers/2008/09/msg2307230.html
I need to update configure_requires appropriately.
Best,
David
On Sep 28, 2008, at 03:34, Eric Wilhelm wrote:
Anyone want to try to tackle this? I think it consists mostly of
searching for qr/1\.2/ in the source and checking whether we are
missing anything vs the new spec.
http://rt.cpan.org/Ticket/Display.html?id=37478
Index: Base.pm
Well then, should I just put 0.30 in configure_requires?
Best,
David
Sent from my iPhone
On Sep 28, 2008, at 11:54, Eric Wilhelm [EMAIL PROTECTED]
wrote:
# from David E. Wheeler
# on Sunday 28 September 2008:
On Sep 28, 2008, at 10:48, Ken Williams wrote:
I don't see anything in our
On Sep 17, 2008, at 11:48, David E. Wheeler wrote:
On Sep 16, 2008, at 15:42, Eric Wilhelm wrote:
While my big warning message might be loud and obnoxious, it:
1. only appears if there is maybe a problem
2. mentions Text::ParseWords and the version number
3. doesn't actually do anything
On Sep 26, 2008, at 19:21, David E. Wheeler wrote:
On Sep 26, 2008, at 18:48, Eric Wilhelm wrote:
I would rather it just be a hash. The ({}) thing is redundant.
You mean you'd rather it be a list. I agree, but it needs to be a
hashref in order to disambiguate it from the original calling
On Sep 27, 2008, at 14:11, Michael G Schwern wrote:
Try using diff -b. It filters out whitespace changes making it
easier to see
the significant changes.
I used `svn diff -x '-ub'. Attached.
At the risk of starting a flamewar, can we reindent the whole thing
at 4
characters? The 2
On Sep 25, 2008, at 22:40, Eric Wilhelm wrote:
$ build
Can't use an undefined value as a HASH reference at
/usr/local/perl/5.10.0/lib/5.10.0/Module/Build/Base.pm line 3679.
...which Module::Build should probably tell you about earlier.
Hi all,
Anyone looking for a small task to get their
On Sep 26, 2008, at 15:26, Michael G Schwern wrote:
Yeah, in this case it's installdirs().
Simplest thing might be to add an optional check/normalizing routine
to
add_property().
__PACKAGE__-add_property(installdirs = site,
sub {
return 1 if /^(core|site|vendor)$/;
On Sep 26, 2008, at 18:48, Eric Wilhelm wrote:
I would rather it just be a hash. The ({}) thing is redundant.
You mean you'd rather it be a list. I agree, but it needs to be a
hashref in order to disambiguate it from the original calling syntax,
in order to maintain backward
On Sep 21, 2008, at 18:11, Ken Williams wrote:
That was actually do_create_readme. However, in my case it was
easier to
override _main_docfile.
But _main_docfile() is a private undocumented method, which can (and
very very likely will) change or disappear in future releases of M::B.
It's
On Sep 18, 2008, at 06:54, David Golden wrote:
I'm recreating my Windows smoker with a fresh copy of Strawberry and
installing the bleeding edge of major toolchain modules. (CPAN,
EU::MM, Test::More, T::H, etc.)
Should I install M::B now from svn or wait for a CPAN dev? I can just
imagine
On Sep 16, 2008, at 15:42, Eric Wilhelm wrote:
While my big warning message might be loud and obnoxious, it:
1. only appears if there is maybe a problem
2. mentions Text::ParseWords and the version number
3. doesn't actually do anything.
Well, no, it removes a test.
4. can be
On Sep 15, 2008, at 17:23, Eric Wilhelm wrote:
Module::Build::Base is about four times as big as it should be and
just
looking at the quoting bugs makes me want to take a chainsaw to all of
the following:
run_perl_script() - has never been documented
run_perl_command() - has never been
On Sep 12, 2008, at 00:10, Eric Wilhelm wrote:
Hi all,
I've backed-out r10222 and r10224 and shipped 0.2808_04.
Unless somebody points out that this has the exploding chipmunk nature
in the next couple of days, I think it is safe to say we can ship 0.29
before Monday. (I'm tempted to bump
On Sep 12, 2008, at 10:45, Jonas Brømsø Nielsen wrote:
Hiya,
I have for long wanted to get my hands dirty with M::B, I have made
several subclasses, but I would like to get more into depth with M::B.
So if there is anything I could do, I would gladly help and
hopefully I could help to
On Aug 31, 2008, at 12:04, Eric Wilhelm wrote:
I can bump the version and ship an alpha without much pain. I've
given
up trying to know whether an official release will break something
though.
When you were keeping track, what issues remained?
Best,
David
On Sep 1, 2008, at 14:48, Eric Wilhelm wrote:
When you were keeping track, what issues remained?
I think we concluded that this was null
my $pm_info = Module::Build::ModuleInfo-new_from_file(
- $file, (defined($mod) ? (module = $mod) : ())
+ $file, # bah: (defined($mod) ?
On Aug 4, 2008, at 04:14, Shlomi Fish wrote:
Um, nothing has to parse Build.PL.
Parse and modify Build.PL
I agree with you: nothing should do that.
So you agree that I should not edit META.yml directly?
Yes.
In this case I want
something machine-readable as input to M::B, which will
On Aug 2, 2008, at 07:17, Shlomi Fish wrote:
http://xrl.us/bi6n9 (link to svn.berlios.de) is a functional spec
for a way to
tag and classify CPAN modules. Those tags and catgories should end
up in the
META.yml. However, inserting them by hand by editing the Build.PL
will be:
You are
On Aug 2, 2008, at 13:40, David E. Wheeler wrote:
2. Not capabale of being manipulated by an external program - Only
perl can
understand Perl, etc..
It looks like M::B does not current put the keywords into the
META.yml file when you run `make distmeta`. It ought to.
Actually, I
On Jul 17, 2008, at 03:54, John Peacock wrote:
Are you seeing that with 0.2808_02, 'cause I'm not?
Bah! I had only installed it for perl 5.10. Stupid! Sorry.
Just installed it for 5.6.2, and now I get this:
benedict% /usr/local/perl-5.6.2/bin/perl Build.PL
Checking whether your kit is
On Jul 17, 2008, at 10:45, Ken Williams wrote:
On Thu, Jul 17, 2008 at 12:37 PM, David E. Wheeler [EMAIL PROTECTED]
wrote:
Checking prerequisites...
Invalid prerequisite condition '4.e-02' for Pod::Readme at
lib/Module/Build/Base.pm line 1262.
What did your dependency line for Pod::Readme
On Jul 16, 2008, at 19:58, Andreas J. Koenig wrote:
Thanks, this indeed solved the problem. I've now installed both
CPAN::Reporter 1.16_51 and Module::Build 0.2808_02 on most of my
smokers. The first PASS has arrived:
http://www.nntp.perl.org/group/perl.cpan.testers/2008/07/msg1902249.html
On Jul 9, 2008, at 00:29, Eric Wilhelm wrote:
# from David E. Wheeler
# on Thursday 19 June 2008 12:25:
For my install of File::Path on Perl 5.10, it
won't actually delete a directory if your current cwd is unknown.
So I
added appropriate calls to `chdir` when `Cwd::getcwd` returns
false
On Jul 9, 2008, at 01:13, Eric Wilhelm wrote:
Shouldn't this be:
__PACKAGE__-add_property(use_tap_harness = 0);
(instead of)
__PACKAGE__-add_property(use_tap_harness = {});
So the --use_tap_harness=1 command-line option will work?
Yes, good catch. Pasto.
(For some value of 'work' --
On Jul 9, 2008, at 01:30, Eric Wilhelm wrote:
I added an automagic $dist-chdir_original() to the remove() method
and
changed all of the tests to use $dist-chdir_in().
David, please try r11502 and let me know if this passes on your 5.10.
Will do sometime today.
Best,
David
On Jul 9, 2008, at 09:52, David E. Wheeler wrote:
On Jul 9, 2008, at 01:30, Eric Wilhelm wrote:
I added an automagic $dist-chdir_original() to the remove() method
and
changed all of the tests to use $dist-chdir_in().
David, please try r11502 and let me know if this passes on your 5.10
On Jul 9, 2008, at 09:55, David E. Wheeler wrote:
Yes, you fixed it. Thanks! I'll submit a new patch for the
TAP::Harness stuff alone today.
And here it is. Executive summary cribbed from before:
* Documents the `test_file_exts` property and makes it actually
work. Note that, as a side
On Jul 9, 2008, at 10:34, Eric Wilhelm wrote:
I found it being done in _optional_arg(). Am I the only one who
thinks
this could use some better documentation?
You're not.
The chase to understand options currently leads through quite a few
uncommented functions. Did I miss a memo with
On Jul 9, 2008, at 10:15, Eric Wilhelm wrote:
TAP::Harness doesn't force the caller's @INC into subprocesses the way
Test::Harness did, so it needs to be explicitly passed as 'libs =
[EMAIL PROTECTED]' -- though we might want to clean that up a bit to have e.g.
only 'blib/lib'?.
Makes sense
On Jul 9, 2008, at 11:43, Eric Wilhelm wrote:
Makes sense to me. Though it did work fine the way I had it. I wonder
why it wasn't a problem?
You were not running './Build test --use-tap-harness' for
Module::Build
because I am still sitting on the make-that-an--option code.
The test I
On Jul 9, 2008, at 11:49, David E. Wheeler wrote:
You were not running './Build test --use-tap-harness' for
Module::Build
because I am still sitting on the make-that-an--option code.
The test I wrote uses it, though (as a boolean), and it runs tests.
Oh! The tests run by the tests have
On Jul 9, 2008, at 18:47, Ron Savage wrote:
Hi Eric
Pick the odd one out :-):
Everybody hates:
o Module::Signature
o Development-style version numbers
o Thread implementations which don't work
o XYZ implementations which don't work
o Less than infinitely fast response times
o MS Win2FK
o MS
On Jul 9, 2008, at 17:29, Eric Wilhelm wrote:
The new file '.perl_developer.yml' in the trunk is to allow me to type
publish_module and ship Module::Build.
0.2808_02 is out now. We should have rolled about 15 alphas between
whenever the heck it last shipped and now.
Can we get _03 out now,
On Jul 8, 2008, at 17:23, David Golden wrote:
require 5.005_62; # at the top of Makefile.PL
I believe that M::B::Compat in 0.2808_01 will do this for you if you
are having M::B generate your Makefile.PL.
Is that released yet? If not, why not?
Thanks,
David
On Jun 24, 2008, at 03:42, David Golden wrote:
That's a great point. The Oslo Consensus (from the Oslo QA hackathon)
agreed on supporting 'perl' as a special key for requires,
configure_requires, etc. Having that enshrined in the META.yml spec
would be a great way to ratify that sentiment.
On Jun 23, 2008, at 19:59, Ken Williams wrote:
Hearing none, I'll entertain a motion to copy
http://module-build.sourceforge.net/META-spec-blead.html to
http://module-build.sourceforge.net/META-spec-v1.4.html .
+1
David
On Jun 18, 2008, at 11:07, Eric Wilhelm wrote:
Link?
http://www.nntp.perl.org/group/perl.module.build/2008/03/msg1298.html
Wow, that's pretty comprehensive. I'm afraid that I'm much too lazy to
implement plugins as described there. Besides, to get Module::Build to
do what I want, I'd
On Jun 18, 2008, at 01:57, Eric Wilhelm wrote:
so I guess that subclassing isn't
necessarily the best way to go.
Do you have enough tuits to dust-off the plugin architecture thread?
Link?
How hard can it be? (He asks, ignoring the dragons.)
Subclassing is not a great way to do mixins by
Howdy,
I've just sent a patch to Andy Armstrong for TAP::Harness that will
allow me to mix different kinds of tests in a single harness (Perl,
Ruby, SQL, whatever), just as long as they all emit TAP, of course.
I'd like to take advantage of this in my Build scripts. It looks like
the
On May 22, 2008, at 00:06, Adam Kennedy wrote:
Gee, I thought it was finalized. I've added it to all of my modules
and it's included in my META.yml thanks to the version of
Module::Build that ships with Perl 5.10.
All the modules have implemented it, CPANPLUS was the last and added
it on
On May 20, 2008, at 21:20, Eric Wilhelm wrote:
# from David Golden on Tuesday 20 May 2008:
On Tue, May 20, 2008 at 11:03 PM, Adam Kennedy
Personally, I'd like to see configure_requires: finalised first
before we start dealing with test_requires, so that we have the
option of solutions that
Howdy,
I'm working on a series of modules for a client. We developers need a
bunch of test modules, but OPS will want to just install the module
without running tests.
I've been putting the test module requirements into `build_requires`:
configure_requires = { 'Module::Build' =
On Jan 22, 2008, at 10:23, David E. Wheeler wrote:
I didn't see it in Changes, so I though I'd ask here: In what
version of M::B was `configure_requires` added?
Oh, I see, it hasn't been released yet. But it is in the Perl 5.10
release.
Best,
David
On Nov 11, 2007, at 11:07, Eric Wilhelm wrote:
I would like to have a shorter Build.PL for cases where a distribution
contains no modules. That is, it consists of just qw(Build.PL bin/
foo)
(and maybe 't/basic.t'.)
Dude. Don't you put all of your code in modules and make bin/foo a
thin
On Sep 4, 2007, at 18:00, Michael G Schwern wrote:
Anyone still using test.pl with Module::Build should be hit with a
hammer anyway.
*cough*DBI*cough*
Yeah, okay, it doesn't use Module::Build yet, but it has a very
specific reason for supporting test.pl in addition to t/. How should
On Apr 19, 2007, at 05:04, Ken Williams wrote:
Is there some reasonable way (on reasonable platforms) to figure
out if the terminal is ANSI-color capable? I was looking at
Term::Cap and I almost went cross-eyed. It would be nice to have
snazzy help output, but we don't want to put
On Oct 11, 2006, at 11:28, Ken Williams wrote:
Craniosynostosis:
http://www.cappskids.org/CranioFAQ.htm
Wow. That's a new one to me.
He's doing awesome now, I just picked a few of his dissolvable
stitches out a few minutes ago. =)
Very glad to hear it.
Best,
David
80 matches
Mail list logo
