Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • B Bio-DB-HTS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • Bio-DB-HTS
  • Issues
  • #75

Closed
Open
Created May 01, 2018 by Marek Szuba@mks

Illegal versioning scheme

Created by: mkszuba

The current Bio-DB-HTS versioning scheme is, sadly, incompatible with what Perl expects, and according to a Perl-veteran colleague of mine it is in fact illegal on CPAN, where this module has been present since version 2.10. Specifically, Perl runtime expects version numbers in the form of x.yy to be floating-point numbers - meaning that from the runtime's point of view, 2.10 == 2.1 < 2.9.

Demonstration:

  1. Install Bio-DB-HTS version 2.10
  2. perl -e 'use Bio::DB::HTS 2.5'

Expected result: in the current versioning scheme 2.10 > 2.5 so it should work.

Actual result: "Bio::DB::HTS version 2.5 required--this is only version 2.10".

At least as far as CPAN is concerned there is no actual violation yet (2.10 < 2.11), however there might be trouble once the module has reached version 2.20 according to the current scheme.

Assignee
Assign to
Time tracking