David Golden wrote:
> On Sun, Jun 14, 2009 at 2:50 PM, Eric Wilhelm
> wrote:
>> I'm sure that's all "no problem" with git, but it is some non-zero
>> amount of work for me to update the process (vs zero amount of work for
>> me if it doesn't change.) We want to keep releases *easy*, so please
>>
David Golden wrote:
On Tue, Jun 16, 2009 at 9:33 PM, Elliot Shank wrote:
So, kindly don't put M::B into the build requirements if building M::B
itself.
Interesting. The new behavior to automatically include M::B as a
configure_requires if there is no configure_requires probably needs an
excep
On Tue, Jun 16, 2009 at 9:33 PM, Elliot Shank wrote:
> When our continuous integration machine starts with a stock 5.10.0 and tries
> to upgrade M::B, CPAN.pm sees a build requirement on 0.33_01 and suspends
> the build to follow the dependency, which leads to a new build with a build
> requirement
When our continuous integration machine starts with a stock 5.10.0 and tries to
upgrade M::B, CPAN.pm sees a build requirement on 0.33_01 and suspends the
build to follow the dependency, which leads to a new build with a build
requirement on 0.33_01...
Thankfully, we've got a timeout on that b
On Sun, Jun 14, 2009 at 2:50 PM, Eric Wilhelm wrote:
> I'm sure that's all "no problem" with git, but it is some non-zero
> amount of work for me to update the process (vs zero amount of work for
> me if it doesn't change.) We want to keep releases *easy*, so please
> include the above in any tran
On Jun 16, 2009, at 4:47 PM, Michael G Schwern wrote:
svn cp repo/trunk repo/tags/$taggit tag $tag -m 'Optional message'
You'll also want to push the tag back upstream. I do this:
git tag -a $tag
git push --tags
Best,
David
Curtis Jewell wrote:
> And I will say this:
>
> I know it's not horribly important, but switching to git, especially
> without using something like github, is almost a non-starter for a
> Windows Perl user.
>
> The reason being that Msys-git (the one native version of git for
> Windows) installs
Eric Wilhelm wrote:
> # from Michael G Schwern
> # on Saturday 13 June 2009 21:33:
>
>> +MAX_INT
>>
>> I can do it, I've done it often enough and I think the MB repo is
>> pretty simple
>
> My concern is still for the release process. I need to be able to
> easily pull a sequential log of commi
Situation:
-- Perl with Module::Build 0.2808
-- CPAN::Reporter::Smoker specifies Module::Build 0.30 as 'requires'
-- CPAN.pm runs Build.PL (0.2808) sees the requires
-- CPAN.pm installs Module::Build (0.33)
-- CPAN.pm runs C::R::S Build (0.33)
-- Build dies due to version mismatc
