Greg Sabino Mullane wrote:
Which reminds me: we have a dependency on version.pm? Whatever for?
So we can use versions such as '2.18.1'. You know, like other projects
do, such as Postgres, git, and Perl. Yeah, yeah, I know all about
the workarounds, shortcomings, and debates regarding versioning in
Perl. Discussion could make our Unicode thread look tame in
comparison. :) Using version.pm is an easy way out of the mess. I'm
open to arguments for not using it, but you better bring
strong ones.
What I do in my recent projects is not use version.pm but rather use the older
fractional number versions that version.pm or Perl consider are equivalent to
the versions you want.
So, for example, you can drop the version.pm dependency and declare your version
as 2.018001 instead of what you said, and they would compare as being equal.
You mention "Perl itself" but for example the current production Perl version is
5.014002.
This seems like the simplest best solution to me.
Stuff like version numbers isn't a strong enough reason to add a dependency to
DBD::Pg, especially since version.pm has its own dependencies as I recall. On
the other hand, the worst of this has been resolved a few months ago, as the
latest version.pm in CPAN no longer requires Module::Build.
-- Darren Duncan
