-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Comments
I just upgraded to
|
I'll take a closer look at all this within the next couple of days. On 30/05/2016 10:34, protist wrote:
|
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. |
Thank you for that! However, after installing the latest release (tagged 3.2.20160530), the command line version is still off by one.
I built this at local time 31 May, so I'm not sure if that is relevant. |
Is there some way to find the numeric version number of an older version?
|
@averagehat I investigated a bit further, also in relation to my (unanswered) comment above. It seems that the version supplied by @stephaneguindon I rebuilt and installed the latest version, and now it's showing a different internal version, which is derived from today's date.
|
According to tags, the latest stable release is 3.2.0. However, after installing, the version reported is different.
For package management and users knowing if they were up-to-date, I was wondering if these two could be synchronised, please?
The text was updated successfully, but these errors were encountered: