# from Christopher J. Madsen
# on Thursday 28 February 2008 23:34:
>Module::Build::Dist:
> Making the trivial changes outside of version control
> that I've described here (VERSION sections & README)
Ok, but why is that not also a separate developer tool?
Note: one trouble with the "eval {req
# from Adam Kennedy
# on Friday 29 February 2008 00:31:
>> http://scratchcomputing.com/svn/CPDK/trunk
>
>We've all got the same thing...
>
>I just call mine ADAMK::Starter, ADAMK::Release and don't put them on
>the CPAN :)
http://scratchcomputing.com/svn/CPDK/trunk/bin/publish_module
http://sc
# from Michael G Schwern
# on Friday 29 February 2008 02:07:
>> The Test::Run Build.PL contains a 'dist_version_from' key.
>> Furthermore, 0.0114 received 23 passes, so it should work:
>>
>> http://cpantesters.perl.org/show/Test-Run.html#Test-Run-0.0114
>>
>> So Something seems wrong with your sys
On Thu, Feb 28, 2008 at 11:47 PM, Christopher J. Madsen <[EMAIL PROTECTED]>
wrote:
> As I was about to check in these changes, I realized that's the wrong
> way to do it. I want these features in all my modules, and I don't want
> to have to copy & paste them into My_Build subclasses. And I'l
David Golden wrote:
On Thu, Feb 28, 2008 at 11:47 PM, Christopher J. Madsen <[EMAIL PROTECTED]>
wrote:
As I was about to check in these changes, I realized that's the wrong
way to do it. I want these features in all my modules, and I don't want
to have to copy & paste them into My_Build sub
On Fri, February 29, 2008 2:07 am, Eric Wilhelm wrote:
> # from Christopher J. Madsen
> # on Thursday 28 February 2008 23:34:
>
>>Module::Build::Dist:
>> Making the trivial changes outside of version control
>> that I've described here (VERSION sections & README)
>
> Ok, but why is that not also
On Fri, February 29, 2008 1:53 am, Adam Kennedy wrote:
> Christopher J. Madsen wrote:
>> Adam Kennedy wrote:
>>
>>> This now means that installing modules from the tarball has a different
>>> result from installing the module from version control.
>>>
>>
>> True, but if you install from version con
On Thu, Feb 28, 2008 at 11:55 AM, Eric Wilhelm
<[EMAIL PROTECTED]> wrote:
> # from David Golden
> # on Thursday 28 February 2008 04:43:
>
>
> >[1] Whether it's a good approach the way Module::Build sets features
> >at install time versus picking up optional modules later is a
> >separate, debat
On Thu, Feb 28, 2008 at 4:06 PM, Michael G Schwern <[EMAIL PROTECTED]> wrote:
>
> A simple solution is to add easy module bundling to Module::Build which will
> honor a higher external version. MakeMaker already does just this for itself
> with things like ExtUtils::Install and ExtUtils::Manife
On Fri, Feb 29, 2008 at 1:04 PM, Ken Williams <[EMAIL PROTECTED]> wrote:
> Keep in mind that the only easy use case for it is for build_requires
> stuff. True runtime requirements ought to still be fetched from CPAN
> as per usual.
Nit: also for configure_requires.
David
# from Shlomi Fish
# on Friday 29 February 2008 05:55:
>No. dist_version_from points to:
>
>dist_version_from => "lib/Test/Run/Core.pm",
Oh. So module_name is set, but doesn't correspond to dist_version_from.
That's a different case, and apparently also one for which there was no
coverage.
I
Eric Wilhelm wrote:
# from Shlomi Fish
# on Friday 29 February 2008 05:55:
No. dist_version_from points to:
dist_version_from => "lib/Test/Run/Core.pm",
Oh. So module_name is set, but doesn't correspond to dist_version_from.
That's a different case, and apparently also one for which there
On Fri, Feb 29, 2008 at 1:21 PM, David Golden <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 29, 2008 at 1:04 PM, Ken Williams <[EMAIL PROTECTED]> wrote:
> > Keep in mind that the only easy use case for it is for build_requires
> > stuff. True runtime requirements ought to still be fetched from CPAN
13 matches
Mail list logo
