-
-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
souper: 2017-03-07 -> 2017.03.23 #25683
Conversation
* update to latest * change version format for nix-env friendliness.
This is giving me deja vu. I feel like I had a debate with a reviewer on the PR that added this in which I set the version to |
Input welcome! It seems familiar to me as well, hopefully this can be agreed on quickly :). Don't see any mention of it in the PR that was first merged with Souper, though: #22468 (I bounced through the CONTRIBUTORS.md before submitting because I recall there being some rule/standard/suggestion but I can't find it now...) |
Hmm, why is 2017.03.23 more nix-env friendly? Also https://nixos.org/nixpkgs/manual/#sec-package-naming |
Darn, sorry I couldn't find that document. Knew it existing somewhere. Will drop the version change portion. The "more nix-env friendly" claim seems to be at least partially untrue: apparently it's the shell completion that doesn't work nicely with the hyphenated dates as version strings. I have no evidence nix-env itself handles dots and differently than hyphens, my mistake. |
Closing in favor of #25687, sorry folks. |
For future reference, there is no problem force pushing revised commits in a pull request branch. Just also make a comment saying that you did a force push as it is easy to miss for people watching the PR ☺ |
Looking at how And regarding force-push, you got it 👍. |
Yeah, you can double confirm this using
|
Motivation for this change
Things done
(nix.useSandbox on NixOS,
or option
build-use-sandbox
innix.conf
on non-NixOS)
nix-shell -p nox --run "nox-review wip"
./result/bin/
)