-
-
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
haskell-modules: update tensorflow for 1.14 #67952
Conversation
cabal2nix . --subpath $f | ||
echo ') {};' | ||
done | ||
echo }) | sed 's1src = ./.;1src = tensorflow-haskell-src;1' | nixfmt |
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.
It would be great if there was a separate updater script that basically did the above.
A bunch of other places in nixpkgs have an actual updater script that bumps versions and re-runs commands like this.
Having a script like this would make it much easier for other maintainers to keep the tensorflow stuff updated.
Where do the packages listed in |
@@ -0,0 +1,310 @@ | |||
{ fetchFromGitHub }: |
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 was thinking that these tensorflow packages could probably go in the non-hackage-packages.nix
file (since that is what they are), but if you also add an update script, it might just be easier to keep them in a separate file (so tensorflow-packages.nix
as you currently have it).
@GrahamcOfBorg build haskellPackages.tensorflow haskellPackages.tensorflow-core-ops haskellPackages.tensorflow-logging haskellPackages.tensorflow-opgen haskellPackages.tensorflow-ops haskellPackages.tensorflow-proto haskellPackages.tensorflow-records haskellPackages.tensorflow-records-conduit haskellPackages.tensorflow-test |
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.
Why does this PR package non-Hackage versions of those packages?
Shouldn't we distribute released versions?
@peti It looks like the tensorflow libraries don't build with the latest I have confirmed that all the packages from this PR build correctly, but I imagine it might just be easier for us to wait until upstream merges in the above PR and makes a new release. When that happens we will be able to get rid of the stuff from this PR. |
I've asked upstream to do a release |
I've updated the tensorflow packages so they work with tensorflow 1.14.
Please let me know if there is a better way to put this in nixpkgs.
Notify maintainers
cc @basvandijk @peti