Ken Williams wrote:
On Oct 8, 2006, at 10:50 PM, Adam Kennedy wrote:
o I now think Adam mistook my comments as personal criticism and
over-reacted. My apologies if I caused the problem, but I fear Adam
is hyper-sensitive since Data::package is one of his
I'll admit I take some issue to call
On Oct 8, 2006, at 10:50 PM, Adam Kennedy wrote:
o I now think Adam mistook my comments as personal criticism and
over-reacted. My apologies if I caused the problem, but I fear
Adam is hyper-sensitive since Data::package is one of his
I'll admit I take some issue to calling a perfectly nor
On Oct 8, 2006, at 5:49 PM, Ron Savage wrote:
o Just for the record, at $work, I checked several machines and
they all had 2
versions of Perl installed, but in each case I only checked the
compiler used
for the Perl I use, and in each case it was absent. This is a PITA,
of course,
and since
On Oct 8, 2006, at 10:59 PM, Adam Kennedy wrote:
The only downside of this approach is that it requires a CPAN
module for every external system. This is probably quite reasonable
for the top 20 cases and for complicated cases (such as "do I have
a C/XS/etc compiler") but might not be ideal
On Oct 8, 2006, at 11:32 PM, Adam Kennedy wrote:
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,
On Oct 9, 2006, at 1:39 PM, Andreas J. Koenig wrote:
Recent CPAN shells have the "failed" command that sums up which
problems have been encountered in the current session.
Per default a summary of the problems during every command is printed
before the next prompt.
And by turning on color you
On Tue, 10 Oct 2006 01:13:17 +1000, Adam Kennedy wrote:
Hi Adam
> If this is all going to be held in some external system outside the
> META.yml , which is what read the above as going with now, then by
> all means. This is all perfectly workable and fine, changing it
> down the track is just fin
> On Sun, 08 Oct 2006 20:35:29 -0700, Michael G Schwern <[EMAIL PROTECTED]>
> said:
> That's a problem which can be solved by the CPAN shells through
> better error reporting and its not unique to this issue.
Recent CPAN shells have the "failed" command that sums up which
problems
Ron Savage wrote:
On Sun, 8 Oct 2006 16:58:50 -0700, Eric Wilhelm wrote:
Hi Eric
How about doing this with an external tool (i.e. a utility or
Sure, that's OK.
What info will it put in the meta data?
I can't say exactly, but I'm thinking that some general principles could be
enunciated
Adam Kennedy wrote:
>> The only thing left is to make it clear to authors that they must add
>> CBuilder to build_requires if their distro uses M::B features that
>> need it. Documentation is the weak remedy. An automatic error during
>> "./Build dist" is the strong remedy.
>
> Or take the M:I a
On Sun, 08 Oct 2006 17:54:55 -0700, Michael G Schwern wrote:
Hi Michael
> 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 Alie
On Sun, 8 Oct 2006 16:58:50 -0700, Eric Wilhelm wrote:
Hi Eric
> How about doing this with an external tool (i.e. a utility or
Sure, that's OK.
> What info will it put in the meta data?
I can't say exactly, but I'm thinking that some general principles could be
enunciated /and/ followed:
o S
# from Marvin Humphrey
# on Sunday 08 October 2006 11:31 pm:
>> An automatic error during "./Build dist" is the strong remedy.
>To follow the automagic-add approach out ad absurdum, should it ?
>automatically detect that you need other things besides CBuilder?
Maybe. But, we're talking about co
13 matches
Mail list logo
