Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the FusionInventory-Agent CPAN distribution.

Report information
The Basics
Id: 61282
Status: resolved
Priority: 0/
Queue: FusionInventory-Agent

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 2.1.3
Fixed in: (no value)



Subject: changing version number format considered harmful
2.1 > 2.1.3 according to version number logic. Why this is so and why you should never change the format of your version numbers, please read on David Golden's article Version numbers should be boring http://www.dagolden.com/index.php/369/version-numbers-should-be-boring/ The price you pay is that 2.1.3 is not indexed but 2.1 is. HTH, Thanks && Regards,
On Sun Sep 12 03:34:50 2010, ANDK wrote: Show quoted text
> 2.1 > 2.1.3 according to version number logic. > Why this is so and why you should never change the format > of your version numbers, please read > on David Golden's article
I would say instead, Why is it so hard for CPAN to compare version number? :( Are you sure there is a problem with that. It looks ok there: http://search.cpan.org/dist/FusionInventory-Agent/ Regards,
Show quoted text
glb> I would say instead, Why is it so hard for CPAN to compare version glb> number? :(
Good question. Show quoted text
glb> Are you sure there is a problem with that. It looks ok there: glb> http://search.cpan.org/dist/FusionInventory-Agent/
I don't know the exact tricks that search.cpan.org is using. On the distribution level it must have heuristics. Since both F/FU/FUSINV/FusionInventory-Agent-2.1.3.tar.gz and F/FU/FUSINV/FusionInventory-Agent-2.1.tar.gz are indexed. The majority of modules in F/FU/FUSINV/FusionInventory-Agent-2.1.3.tar.gz have no version number so are indexed according to the date. But the one module that has a version number is FusionInventory::Agent and it has the version numbers '2.1' and '2.1.3', respectively. Your users will not get a newer version of FusionInventory::Agent when they ask the toolchain to upgrade their perl. They will not get a newer version when they simply say 'install FusionInventory::Agent', It's due to the arithmetics of perl version numbers. Try perl -le 'use version;print map { "$_\n"} sort { version->new($a) <=> version->new($b);} @ARGV' 2.1 2.1.3 2.100.1 2.1.3 2.1 2.100.1 HTH, Regards,
On Sun Sep 12 16:38:22 2010, ANDK wrote: Show quoted text
> I don't know the exact tricks that search.cpan.org is using. On the > distribution level it must have heuristics. Since both > F/FU/FUSINV/FusionInventory-Agent-2.1.3.tar.gz and > F/FU/FUSINV/FusionInventory-Agent-2.1.tar.gz are indexed. > > The majority of modules in > F/FU/FUSINV/FusionInventory-Agent-2.1.3.tar.gz have no version number > so are indexed according to the date.
I removed the 2.1 tarball from FUSINV CPAN space. We will use the 2.2.0 version for the new major release. Thank you Andreas for taking the time to point out the problem with our distribution. Best regards, Gonéri
Sorry to be a pain in the neck. Cosider that 2.2.0 does not solve the problem for your current user community: % perl -le 'use version;print map { "$_\n"} sort { version->new($a) <=> version->new($b) } @ARGV' 2.1 2.1.3 2.100.1 2.2.0 2.2 2.99.42 2.200.0 2.1.3 2.2.0 2.99.42 2.1 2.100.1 2.2 2.200.0 Look, where '2.2.0' is. If they have 2.1, they only can upgrade to something around 2.100.1 or higher. Or you go back to '2.2'. Or to 3. Try it out with the oneliner above before you make a decision. Thanks!
On Mon Sep 13 21:08:59 2010, ANDK wrote: Show quoted text
> Sorry to be a pain in the neck. Cosider that 2.2.0 does not solve the > problem for your current user community:
Show quoted text
> Look, where '2.2.0' is. If they have 2.1, they only can upgrade to > something around 2.100.1 or higher. Or you go back to '2.2'. Or to 3.
I'm really not fan of these alternative as we want to release a fix release. Since FusionInventory::Agent is a application, I don't think it's critical if it don't get upgraded automaticly. For the futur we will take care to avoid this situation again. Best regards
Hi, Since 2 years now, we take care of the format of the version of FusionInventory distribution. I think I can close the bug now. Thank you for the helpful bug report, Cheers