-
Notifications
You must be signed in to change notification settings - Fork 116
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
Guix v0.18.1 #1076
Guix v0.18.1 #1076
Conversation
✅ Deploy Preview for elastic-ritchie-8f47f9 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
(string-append "(def (gerbil-version-string) \"" ,gerbil-stamp-version "\")\n"))) | ||
(display "... write ") (display gerbil-version-path) (newline) | ||
(call-with-output-file `(path: ,gerbil-version-path create: maybe append: #f truncate: #t) | ||
(lambda (port) (display gerbil-version-text port)))))))) |
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.
Go away post-#1074
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.
Go away post-#1074
I do not see a MANIFEST file in every single commit, nor is there one in my test builds. Am I missing something? How does that file get created if I am building from HEAD without git?
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.
There will be a MANIFEST file on git iff the commit is a release.
On the other hand, you can have Guix create its own MANIFEST file to build without git.
That's how my upcoming Nix build will work: no more fancy patches, just create a MANIFEST.
Create your own local one with ./manifest.sh.
No description provided.