[Padre-dev] [Padre-commit] rev 1309 - trunk

[Adam Kennedy]

Because it doesn't mean "we are not sure", it means "we need any
version ever released".

Normally they are only used for dependencies on long-time core
modules, because any version we could depend on is utterly irrelevant.

The best option for a "we're not sure" version is the most current,
and then push backwards.

There's been many cases where bugs have been found incorrectly,
because someone had a version as zero and a user just happened to
somehow have a really old version. That causes applications to fail
when they shouldn't have.

So in general, always read the Changes file for a module and look for
a reasonable version, otherwise go with the latest. If there's any
problems with the current version, then you explicitly push them back.

Adam K

2008/11/25 Gabor Szabo <szabgab at gmail.com>:
> On Tue, Nov 25, 2008 at 10:08 AM,  <svn at perlide.org> wrote:
>> Author: adamk
>> See also: http://padre.perlide.org/changeset/1309
>> Date: 2008-11-25 00:08:45 -0800 (Tue, 25 Nov 2008)
>> New Revision: 1309
>>
>> Modified:
>>   trunk/Build.PL
>> Log:
>> Dependencies on zero versions are bad, setting versions for cases where the dep is currently zero
>
> Personally I don't mind "forcing" people to upgrade some of their modules to a
> recent version but can you please explain why zero dependency versions
> are they bad?
>
> To me they only mean
> "We need this module but we are not sure what is the minimum version."
>
> Gabor
> _______________________________________________
> Padre-dev mailing list
> Padre-dev at perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev
>