On 2010.8.22 3:27 PM, Dave Rolsky wrote:
> I made a branch called with-build-tools and checked in the entire build
> directory.
1158:a902109c063f added the Build.PL and 1159:f86836125cf7 removed it. *head
desk*
Add the Build.PL to default where everybody will find it and it will Just
Work. That's it. That's all that's necessary. Any given Perl dev familiar
with CPAN modules should be able to build and test the code out of the
repository without special instructions.
Not in a branch that nobody will find. In default.
> But I really don't see how this is any different than you
> working from the tarball on CPAN. It's effectively the same result.
Like I said in my original post, working from the tarball means its more work
to keep up to date with new releases and parallel developments. If I was
making a trivial patch its not so bad. But its particularly important when
I'm doing things like tearing apart the fundamentals of DateTime.
I change a bunch of stuff, you change a bunch of stuff, I might want to know
about that and merge it in rather than be surprised when a new release comes
out. This is what version control is for.
Sure, I can work around it, but why? Its frustrating, its drag, it turns the
repository into a tool only for the cabal.
And then there's people who are not me. People who see the link to the
repository on search.cpan.org, figure they'll be good and work from the
repository, get frustrated because they can't build the thing and walk away.
There's a very, very small amount of bullshit a new contributor will accept
before quietly dropping out.
If it was a big deal requiring a whole lot of work, that would be something.
We're talking about committing one file that you already have. 30 seconds of
work to make DateTime a little bit easier to contribute to.
You might not think so, but this sort of intangible is important. And the
cost to you is so low its beyond absurd we're even discussing it. This is
like pulling teeth.
--
ROCKS FALL! EVERYONE DIES!
http://www.somethingpositive.net/sp05032002.shtml
