Make sure all the modules have the same version number in a distribution

2013-01-08 Thread Gabor Szabo
Hi, I just wanted to update a distribution and ensure that all the modules in a distribution have version number and they are all the same. I guess Dist::Zilla would do that, but this distribution I am patching use Module::Build. I found Test::HasVersion but as I can see it only checks if there

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread John M. Gamble
On Tue, January 8, 2013 5:15 am, Gabor Szabo wrote: Hi, those of you who read blogs.perl.org probably already saw my posts, but I guess there are many others on this list who are not reading that site. Recently I checked and only 50% of the CPAN distributions have a link to a public

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread David Cantrell
On Tue, Jan 08, 2013 at 10:06:31AM -0600, John M. Gamble wrote: I think the finger should be pointed at h2xs, at least as it stands now. A programmer new to CPAN won't know about the META information, and h2xs just isn't oriented that way. I think the finger should be pointed at

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread John M. Gamble
On Tue, January 8, 2013 10:43 am, David Cantrell wrote: On Tue, Jan 08, 2013 at 10:06:31AM -0600, John M. Gamble wrote: I think the finger should be pointed at h2xs, at least as it stands now. A programmer new to CPAN won't know about the META information, and h2xs just isn't oriented that

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread David Nicol
Recently I checked and only 50% of the CPAN distributions have a link to a public version control system: http://blogs.perl.org/users/gabor_szabo/2013/01/50-of-the-new-cpan-uploads-lack-a-repository-link.html uh, CPAN /is/ a public version control system. You have a favorite VCS and want

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread Olaf Alders
On 2013-01-08, at 1:03 PM, David Nicol wrote: Recently I checked and only 50% of the CPAN distributions have a link to a public version control system: http://blogs.perl.org/users/gabor_szabo/2013/01/50-of-the-new-cpan-uploads-lack-a-repository-link.html uh, CPAN /is/ a public version

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread John M. Gamble
On Tue, January 8, 2013 12:14 pm, Olaf Alders wrote: On 2013-01-08, at 1:03 PM, David Nicol wrote: ... On the other hand, a comprehensive CPAN by git as an additional CPAN feature would have a measure of awesome to it, as an alternate distribution and synchronization method. I don't

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread David Nicol
On Tue, Jan 8, 2013 at 12:14 PM, Olaf Alders o...@wundersolutions.comwrote: uh, CPAN /is/ a public version control system. You have a favorite VCS and want to make diffs easily? Download, unpack, init, add, commit, work, diff. That doesn't sound easy at all. ;) For example, if you want to

Re: license information and link to source code repository from your CPAN distribution

2013-01-08 Thread David Nicol
On Tue, Jan 8, 2013 at 12:28 PM, John M. Gamble jgam...@ripco.com wrote: It was not intended as a constantly synchronized central repository of all of CPAN. That's what I meant, and it was something of a straw man.

Re: Make sure all the modules have the same version number in a distribution

2013-01-08 Thread Ben Deutsch
Hello, I just wanted to update a distribution and ensure that all the modules in a distribution have version number and they are all the same. I guess Dist::Zilla would do that, but this distribution I am patching use Module::Build. I found Test::HasVersion but as I can see it only

Re: Make sure all the modules have the same version number in a distribution

2013-01-08 Thread David Cantrell
On 08/01/2013 19:16, Ben Deutsch wrote: A question of my own: I immediately thought of the single point of truth idiom, and would have written something like this: package My::Sub::Module; use My::Base::Module; our $VERSION = $My::Base::Module::VERSION; or similar. Would this trip up some