Bug #80515 for BGPmon-core-1: Confusing file names

Tue Oct 30 23:58:44 2012 ANDK [...] cpan.org - Ticket created

Subject:

Confusing file names

Excuse me for my intrusion, I have one question. I'm a regular tester on the CPAN and so stumbled upon your packages BGPmon-Analytics-db-1-03.tar.gz, BGPmon-CPM-1-01.tar.gz, BGPmon-Archiver-1-02.tar.gz, BGPmon-CPM-Prefix-Finder-1-02.tar.gz, BGPmon-core-1-04.tar.gz, BGPmon-Client-1-02.tar.gz, and many more All these share a naming convention that's hard to understand. Could you explain what's the rationale? On first sight one gets the impression you replace all dots in version numbers with a minus, is that right? Is there any reason for that? I'm pretty sure that most of CPAN infrastructure will be confused by such a deviation from the CPAN conventions. Please don't get me wrong, I do not want to tell you how you have to do your versioning. I just would like to understand what you're up to. I'm not a user of your package, I just would like to find out whether you understand the CPAN infrastructure and all the consequences of your file naming conventions. Kind of whether your own convention is a feature or a bug. Thank you,

Sun Dec 02 15:47:48 2012 BGPMON [...] cpan.org - Correspondence added

On Tue Oct 30 23:58:44 2012, ANDK wrote: Show quoted text

> Excuse me for my intrusion, I have one question. I'm a regular tester on > the CPAN and so stumbled upon your packages > > BGPmon-Analytics-db-1-03.tar.gz, BGPmon-CPM-1-01.tar.gz, > BGPmon-Archiver-1-02.tar.gz, BGPmon-CPM-Prefix-Finder-1-02.tar.gz, > BGPmon-core-1-04.tar.gz, BGPmon-Client-1-02.tar.gz, and many more > > All these share a naming convention that's hard to understand. Could you > explain what's the rationale? On first sight one gets the impression you > replace all dots in version numbers with a minus, is that right? Is > there any reason for that? I'm pretty sure that most of CPAN > infrastructure will be confused by such a deviation from the CPAN > conventions. > > Please don't get me wrong, I do not want to tell you how you have to do > your versioning. I just would like to understand what you're up to. I'm > not a user of your package, I just would like to find out whether you > understand the CPAN infrastructure and all the consequences of your file > naming conventions. Kind of whether your own convention is a feature or > a bug. > > Thank you,

Hello, Thank you for bringing this to our attention. Some of the minus signs are intentional and, after reading your response, some of them are incorrect. We have several different key features in our modules that we split into separate packages. This is why we have a dash in between the "BGPmon" and the package name, e.g., Bgpmon-Analytics. We have mislabeled the version number, as you pointed out. If I'm not mistaken, it should look like "BGPmon-Analytics.1.03.tar.gz", for example. Would you agree? If so, the updates to our module will follow that convention. Thank you for your help!

Sun Dec 02 15:47:48 2012 The RT System itself - Status changed from 'new' to 'open'

Sun Dec 02 16:32:11 2012 andreas.koenig.7os6VVqR [...] franz.ak.mind.de - Correspondence added

CC:	ANDK [...] cpan.org
Subject:	Re: [rt.cpan.org #80515] Confusing file names
Date:	Sun, 02 Dec 2012 22:31:50 +0100
To:	bug-BGPmon-core-1 [...] rt.cpan.org
From:	Andreas Koenig <andreas.koenig.7os6VVqR [...] franz.ak.mind.de>

"Dan Massey via RT" <bug-BGPmon-core-1@rt.cpan.org> writes: Show quoted text

> Thank you for bringing this to our attention. Some of the minus signs > are intentional and, after reading your response, some of them are > incorrect. We have several different key features in our modules that > we split into separate packages. This is why we have a dash in between > the "BGPmon" and the package name, e.g., Bgpmon-Analytics. We have > mislabeled the version number, as you pointed out. If I'm not mistaken, > it should look like "BGPmon-Analytics.1.03.tar.gz", for example. Would > you agree?

No, the established convention would be BGPmon-Analytics-1.03.tar.gz. Watch the 25 most recent uploads as of right now: TEX/Sys-RevoBackup-0.16.tar.gz BGPMON/BGPmon-core-1-062.tar.gz TEX/Sys-Bprsync-0.17.tar.gz TEX/Linux-Pidfile-0.16.tar.gz FREW/App-Adenosine-2.001001.tar.gz TEX/Sys-CmdMod-0.17.tar.gz TEX/Monitoring-Spooler-0.02.tar.gz SREZIC/Tk-Pod-0.9941.tar.gz TEX/Log-Tree-0.15.tar.gz TEX/Job-Manager-0.16.tar.gz SAPER/RackMan-1.14.tar.gz TEX/Config-Yak-0.22.tar.gz JAW/Term-Pager-1.02.tar.gz GOMOR/Net-SinFP3-1.21.tar.gz SHLOMIF/HTML-Latemp-NavLinks-GenHtml-v0.2.0.tar.gz GOMOR/Net-Frame-Layer-ICMPv6-1.08.tar.gz GOMOR/Net-Frame-Device-1.10.tar.gz GOMOR/Net-Frame-Dump-1.13.tar.gz AWNCORP/Validation-Class-7.900001.tar.gz ROBINS/XML-Rabbit-0.2.1.tar.gz MIKIHOSHI/Acme-PrettyCure-0.085.tar.gz BERNHARD/Crypt-NSS-X509-0.01.tar.gz LOTTZ/Su-0.110.tar.gz TOBYINK/Acme-Loopy-0.001.tar.gz MARTYLOO/DarkSky-API-0.01.tar.gz Show quoted text

> If so, the updates to our module will follow that convention.

Thanks you! Show quoted text

> Thank you for your help!

You're welcome, -- andreas