[OT] Re: Activestate PPMs for DateTime?

[Joshua Hoblitt]

Who is the point of contact for AS on this issue?
-J
--
On Tue, 2 Nov 2004, Dave Rolsky wrote:
On Mon, 1 Nov 2004, Yitzchak Scott-Thoennes wrote:
Not that I'm blaming DateTime; there's plenty of blame to go around.
ActiveState is to blame for (as rumor has it) having someone maybe
sometime completely rewrite their build scripts, instead of just
quickly addressing this deficiency.  DateTime is to blame for using a
build method that doesn't yet have support from a sizable segment of
the potential user base.  Module::Build is to blame for not coming up
with a way to have dependencies honored by Makefile.PL-friendly tools;
indeed, for not listing itself a dependency at all.  And lastly and
most importantly, ExtUtils::MakeMaker is to blame for having such a
hokey mechanism for dependencies in the first place (to whit: run
Makefile.PL and parse out the PREREQ line from the generated
Makefile).  Oh, and lets not leave out CPAN::FirstTime; everything
might work out ok if it would have a default mirror option; see
http://ppm.activestate.com/BuildStatus/5.8-windows/windows-5.8/DateTime-Locale-0.09.txt
Clearly the easiest for AS is to simple install Module::Build and its 
dependencies before trying to build PPMs.

What's the way forward in all this?  I don't know.  I do know that
the Module::Build people are working on what I assume will be a separate
module to parse complex dependency information out of META.yml.  We'll
see how it goes, and if various tools will adopt it.  I don't hold my
breath.
You hold your breath on it getting written, or getting adopted?  It'll get 
written, I'm sure.  Whether people will adopt it is up to them.

-dave
/*===
VegGuide.Org
Your guide to all that's veg.
===*/

[OT] Re: Activestate PPMs for DateTime?

[Dave Rolsky]

On Tue, 2 Nov 2004, John Peacock wrote:
Module::Build already has it's own
way to tell about dependencies but afaik no one uses it except
CPANPLUS.
And what is worse is that the Module::Build dependencies are treated as 
/suggestions/, and will not throw an error if one is not met.  I just got a 
cpantester's report for one of my modules which only works with Perl 5.8.1 or 
better.  Even though I added 'perl = 5.8.1' to the dependencies, 
Module::Build happily went on to try and build/test the module on a 5.6.1 
machine.  I actually have to add 'use 5.8.1' to the top of the Build.PL file 
to correctly bail out.
Actually, M::B is no different fom EU::MM in this regard.  EU::MM will 
install a module which has unmet dependencies.  It's CPAN or CPANPLUS that 
do the enforcement.  If they're not enforcing them properly with M::B 
modules, that obviously needs to be corrected.

-dave
/*===
VegGuide.Org
Your guide to all that's veg.
===*/