Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Versioning inconsistency #31

Closed
protist opened this issue May 29, 2016 · 6 comments
Closed

Versioning inconsistency #31

protist opened this issue May 29, 2016 · 6 comments

Comments

@protist
Copy link

protist commented May 29, 2016

According to tags, the latest stable release is 3.2.0. However, after installing, the version reported is different.

$ phyml-mpi --version
. command-line: phyml-mpi --version 
. This is PhyML version 20160529.

For package management and users knowing if they were up-to-date, I was wondering if these two could be synchronised, please?

@protist
Copy link
Author

protist commented May 30, 2016

I just upgraded to v3.2.20160529 according to the tags. However, the command-line version is slightly different.

$ phyml-mpi --version

. command-line: phyml-mpi --version 

. This is PhyML version 3.2.20160530.

@stephaneguindon
Copy link
Owner

I'll take a closer look at all this within the next couple of days.
Regards,
-Stephane-

On 30/05/2016 10:34, protist wrote:

I just upgraded to |v3.2.20160529| according to the tags. However, the
command-line version is slightly different.

|$ phyml-mpi --version . command-line: phyml-mpi --version . This is
PhyML version 3.2.20160530. |


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#31 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFX0sVOKqM5PjcNM4UkKYYubRoKEP2doks5qGqEngaJpZM4IpSMB.

@stephaneguindon
Copy link
Owner

I've posted a new release. This has tag 3.2.20160530, which should be consistent with what you get from phyml --version. The versionning in PhyML has been a real mess in the past. I intend to stick to the format used here, i.e., majorversion.minorversion.date, from now on.
Hope that make sense,
-Stephane-

@protist
Copy link
Author

protist commented May 30, 2016

Thank you for that! However, after installing the latest release (tagged 3.2.20160530), the command line version is still off by one.

$ phyml-mpi --version

. command-line: phyml-mpi --version 

. This is PhyML version 3.2.20160531.

I built this at local time 31 May, so I'm not sure if that is relevant.

@averagehat
Copy link

Is there some way to find the numeric version number of an older version?
i.e., I have a version from this commit: bdd18a0
I know the "date" version, but need the numeric version for a publication.

$ phyml --version

                                                                         │
. This is PhyML version 20151007.

@protist
Copy link
Author

protist commented Jun 22, 2016

@averagehat I investigated a bit further, also in relation to my (unanswered) comment above. It seems that the version supplied by $ phyml --version is just the date of the build, so for a publication, it's probably not very informative. I can't really help you with the version of the commit, but if it's untagged, you'd probably just have to reference the commit string anyway?

@stephaneguindon I rebuilt and installed the latest version, and now it's showing a different internal version, which is derived from today's date.

$ phyml-mpi --version

. command-line: phyml-mpi --version 

. This is PhyML version 3.2.20160622.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants