-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
Gerbil #32329
Gerbil #32329
Conversation
@@ -4,13 +4,13 @@ | |||
|
|||
stdenv.mkDerivation rec { | |||
name = "gambit-${version}"; | |||
version = "4.8.8-300db59"; | |||
version = "4.8.8-415-g29ed48bb"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need actually numbers instead of git hashes, since hashes cannot be ordered by nix-env
.
Can you switch to date of commit instead of a concrete git hash here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe 415
is already enough?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe 415 is OK.
@@ -7,11 +7,11 @@ | |||
stdenv.mkDerivation rec { | |||
name = "gerbil-${version}"; | |||
|
|||
version = "0.12-DEV-777-gd855915"; | |||
version = "0.12-DEV-836-gcde6802"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here.
@GrahamcOfBorg eval |
Indeed the 415 and 836 are the number of commits and make it easy to order the version numbers. These versions are taken from git describe --tags (stripping the leading v from the tag, so nix recognizes it's version numbers indeed). I can switch to date if you prefer, but the above is what Gerbil natively uses, and that Gambit may use in the future. |
I think if upstream explicitly references commit counts, it is an aceptable style of patchlevel. |
@7c6f434c yes, but version still contains a commit hash in pr you have just merged, not just the patchlevel. |
Well, hash after the patchlevel should not be able to break version
comparison.
|
Motivation for this change
Many notable changes to Gerbil, that itself depends on notable changes to Gambit, have happened in the two months or so since I last upstreamed my changes to nixpkgs.
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)