On Oct 8, 2006, at 10:26 PM, Eric Wilhelm wrote:
An automatic error during "./Build dist" is the strong remedy.
Aside from the fact that I am apparently unable to correctly configure
my mail client, what is wrong with this approach?
http://www.nntp.perl.org/group/perl.module.build/380
Fro
# from Marvin Humphrey
# on Sunday 08 October 2006 08:13 pm:
>An automatic error during "./Build dist" is the strong remedy.
Aside from the fact that I am apparently unable to correctly configure
my mail client, what is wrong with this approach?
http://www.nntp.perl.org/group/perl.module.buil
It seems to me that if a given distro can be built either with a
compiler or without one (e.g. Params::Validate), then the answer to
"does it require a compiler" is a simple "no".
Only if that "either" is across all platforms.
If something, for example, was looking for /proc/ files on Linux, b
On Oct 8, 2006, at 5:54 PM, Michael G Schwern wrote:
Here's an alternative approach. Why make compiler dependencies
special? Treat them like any other alien dependency. How do we do
that? Wrap a module around it. ExtUtils::CBuilder is one example.
I like. Adding ExtUtils::CBuilder as
A key of "needs_compiler" raises the question, "for what language?" "Compiler"
does not necessarily mean "C compiler". PDL likes to have a Fortran compiler,
Inline::Java needs a Java compiler, and so on.
So the value would be a list of languages.
# Any ol C compiler will do
compiler => 'C
Here's an alternative approach. Why make compiler dependencies special? Treat
them like any other alien dependency. How do we do that? Wrap a module around
it. ExtUtils::CBuilder is one example. The various Alien modules are another.
There's already existing wrapper modules for ssh, rsync
# from Eric Wilhelm
# on Sunday 24 September 2006 11:08 am:
>ATM, I've just written this into our build
>subclass, but would be happy to make it a patch if there's interest.
ping.
--
Turns out the optimal technique is to put it in reverse and gun it.
--Steven Squyres (on challenges in interplane
# from Ken Williams
# on Saturday 07 October 2006 10:47 am:
>Yeah, we should at the very least indicate that the user needs to
>install ExtUtils::CBuilder. I'll make that change.
Is it still up to the author to manually declare the ExtUtils::CBuilder
build_requires dependency?
Perhaps Module
# from Ron Savage
# on Sunday 08 October 2006 03:49 pm:
>o I am thinking of some procedure the author, perhaps, could use to
> generate the info to add to the meta data, like so:
>(1) Probe for compiler
>(2) If found, remove compiler's directory from the path, and bugger
> the consequences (if onl
On Sun, 8 Oct 2006 14:41:49 -0500, Ken Williams wrote:
Hi Ken, and Adam
Thanx for your comments.
Having slept on it, I'd like now to recast this as a tragedy (joke) in 3.14159
acts...
Part 1: The story so far
I've tried to understand Adam's viewpoint, and here's what I assume happened:
o I ha
On Oct 7, 2006, at 9:09 PM, Ron Savage wrote:
Hi Ken, Adam
I had a slight suspicion when I first posted that this might be a
can of worms,
and now I know :-(.
Nah, it's not too bad. We can at least solve the problem I'm
suggesting we solve, which I think was your original request too.
11 matches
Mail list logo