NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Ask Ingy (Score:2)
Build systems are usually so customised as to be impossible to please many people with them as it always seems like the engineer contrived a problem to fit the solution they so cleverly created. You might ask Ingerson about a thing he's working on in a similar vein that seems like it has promise but the social engineering part of it will be the most challenging.
cons (Score:3, Interesting)
Damn shame that Parrot's going to remove the need for their work.
Anyway, cons is the mature product and while I've heard good things about it, I've never used it. Hope the scuttlebutt helps :-)
--Nat
Reply to This
Cons & Module::Build (Score:1)
I've been helping Ken a bit with Module::Build and playing with it for some projects. Its really easy to use and right now does most of the basic stuff ExtUtils::MakeMaker does, except that its way easier to customize.
I'm go
D'oh moment (Score:2, Interesting)
In a complex module with prerequisites, you can't do away with "make" unless you can convince all the other developers to do away with make too.
So the advantage seems to be as autarch said - easy to alter build processes, not necessarily doing away with make.
(one thing I'd like to be able to do is stick XS files in lib/path/to/module, rather than in the root directory, but that seems impossible with ExtUtils::MakeMaker, unless I'm doing a Homer).