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

2013-02-19 Thread Aristotle Pagaltzis
* Dominique Dumont domi.dum...@free.fr [2013-02-16 09:45]: As Perl module developer, I'm guilty as charged: I haven't found a practical way to change $VERSION when a file has actually changed :-/ Nor should you. One day I’ll write that article, one day… -- *AUTOLOAD=*_;sub

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

2013-02-19 Thread Yanick Champoux
On 13-02-19 08:30 AM, Aristotle Pagaltzis wrote: One day I’ll write that article, one day… You know how they say there is no time like the present... :-) Do it! `/anick

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

2013-02-16 Thread Yanick Champoux
On 13-02-16 03:39 AM, Dominique Dumont wrote: Le jeudi 10 janvier 2013 19:34:51,yan...@babyl.dyndns.org a écrit : So, yeah, I've embraced the per-dist version, and have lived happily ever after... Well, if you look at that diff [1] provided by CPAN, knowing that only*one* file was

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

2013-02-16 Thread Dominique Dumont
Le samedi 16 février 2013 17:27:10, vous avez écrit : ... now I'm just thinking wild, wild thoughts, but did anybody at any time proposed to have, just like $VERSION, a $DISTRIBUTION variable indicating to which dist the module belongs to? With that, the version mechanisms could be

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

2013-01-15 Thread David Cantrell
On Sat, Jan 12, 2013 at 12:34:15PM +0100, Aristotle Pagaltzis wrote: Applying the same version to all modules within a distribution is a non- obvious precondition for dependency resolution to work 100% reliably in all edge cases. I have notes for an article about it flying around here

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

2013-01-15 Thread Johan Vromans
David Cantrell da...@cantrell.org.uk writes: I'd love to know what those edge cases are, because I can't think of any. My guess is this applies to distributions that contain a number of modules, some (most) of them not relevant to the end user since they're internal to the distribution. If you

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

2013-01-12 Thread Aristotle Pagaltzis
* Lutz Gehlen lrg...@gmx.net [2013-01-09 16:20]: On Tuesday, January 08, 2013 09:04:31 Gabor Szabo wrote: 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. Please excuse this digression, but would you be

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

2013-01-10 Thread Philippe Bruhat (BooK)
On Wed, Jan 09, 2013 at 08:38:55PM +0200, Gabor Szabo wrote: On Wed, Jan 9, 2013 at 5:17 PM, Lutz Gehlen lrg...@gmx.net wrote: Hi Gabor, On Tuesday, January 08, 2013 09:04:31 Gabor Szabo wrote: I just wanted to update a distribution and ensure that all the modules in a distribution have

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

2013-01-10 Thread John M. Gamble
On Wed, January 9, 2013 9:03 pm, David Christensen wrote: There seems to be two competing points of view regarding version numbering for software source code files: 1. Per-file -- a unique version number for each file that increments when that file changes. RCS and CVS use this approach.

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

2013-01-10 Thread yanick
On Thu, Jan 10, 2013 at 10:06:10AM -0600, John M. Gamble wrote: Yeah, after dithering about it for a few days, I went with the philosophy that the package has the version, not the individual modules. For the simple reason that the package as a whole is what's being developed, from the

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

2013-01-09 Thread Lutz Gehlen
Hi Gabor, On Tuesday, January 08, 2013 09:04:31 Gabor Szabo wrote: 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. Please excuse this digression, but would you be so kind to explain why you find this

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

2013-01-09 Thread Gabor Szabo
On Wed, Jan 9, 2013 at 5:17 PM, Lutz Gehlen lrg...@gmx.net wrote: Hi Gabor, On Tuesday, January 08, 2013 09:04:31 Gabor Szabo wrote: 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. Please excuse this

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

2013-01-09 Thread David Christensen
On 01/09/13 07:17, Lutz Gehlen wrote: Hi Gabor, On Tuesday, January 08, 2013 09:04:31 Gabor Szabo wrote: 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. Please excuse this digression, but would you be so

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: 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