Skip to content

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Jun 14, 2019

@vtjnash
Copy link
Member Author

vtjnash commented Jun 18, 2019

bump

@vtjnash vtjnash requested a review from staticfloat June 18, 2019 18:40
@@ -1,12 +1,12 @@
using BinaryBuilder

name = "LibUV"
version = v"1.24.0"
version = v"2-1.24.0-1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm confused by this version number? What does this mean?

Copy link
Member Author

@vtjnash vtjnash Jun 18, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The commit hash below corresponds to the libuv version "2.0.0+1.24.0-julia-1", where 2.0.0 is the major/minor/patch (prerelease)version, +1.24.0 is the bugfix id for the branch version (similar to how we might say julia v1.3-dev+23), -julia is the patch set id, and -1 is the distinguisher to indicate the first build in the series. I shortened it a bit here to just include the numbers that might be currently relevant for Julia.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't want to encode build numbers into the version; this version should only identify the source; the build version numbers get added on later. I'm also not certain we want the 2- at the beginning; shouldn't we just leave this at 1.24.0?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version number is 2, 1.24.0-julia is just the name string of the current head of the branch

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that mean that when the source next changes, we'll have a version string of 3 with a name string of 1.24.0-julia?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it’ll probably be at version 2.0 for years. The next version would usually be 1.24.0-julia-2 then -3, etc.

In this particular case, as soon as this PR is done, I’ll be replacing it with 2+1.29.1-julia-1, but that’s unusual to have the updates so close together.

@staticfloat staticfloat merged commit 30f0d1b into master Jun 19, 2019
@staticfloat
Copy link
Member

I assume you want new binaries of this built, yes?

@vtjnash
Copy link
Member Author

vtjnash commented Jun 19, 2019

yeah, I thought that was automatic

@staticfloat
Copy link
Member

Unfortunately not yet; but we're getting closer. In the meantime, when nothing goes wrong, it's just two command-line invocations for me, so not bad. Here you go: https://github.com/JuliaPackaging/Yggdrasil/releases/tag/LibUV-v2%2B1.24.0-julia%2B0

@giordano giordano deleted the jn/libuv-32211 branch October 27, 2019 21:29
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

Successfully merging this pull request may close these issues.

2 participants