You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nix-env -if https://github.com/DavHau/mach-nix/tarball/2.0.1 -A mach-nix
62
+
nix-env -if https://github.com/DavHau/mach-nix/tarball/2.1.0 -A mach-nix
63
63
```
64
64
65
65
---
@@ -91,7 +91,7 @@ You can call mach-nix directly from a nix expression
91
91
let
92
92
mach-nix = import (builtins.fetchGit {
93
93
url = "https://github.com/DavHau/mach-nix/";
94
-
ref = "2.0.1";
94
+
ref = "2.1.0";
95
95
});
96
96
in
97
97
mach-nix.mkPython {
@@ -131,7 +131,7 @@ Mach-nix can be fine tuned with additional arguments by importing it via `builti
131
131
#### Configure Providers
132
132
**Providers** allow you to configure the origin for your packages on a granular basis.
133
133
134
-
The following 3 providers are available in version 2.0.0:
134
+
The following 3 providers are available in version 2.1.0:
135
135
1.**nixpkgs**: Provides packages directly from nixpkgs without modifying their sources. Has only a few versions available, but has a high success rate and all the nix features, like `cudaSupport` for tensorflow for example.
136
136
2.**sdist**: Provides all package versions available from pypi which support setuptools and builds them via nixpkgs overlays wherever possible to resolve external dependencies. It still supports the nixpkgs specific features no matter which package version is selected. But chances are higher for a build to fail than with the **nixpkgs** provider.
137
137
3.**wheel**: Provides all linux compatible wheel releases from pypi. Wheels can contain binaries. Mach-nix autopatches them to work on nix. Wheels are super quick to install and work quite reliable. Therefore this provider is preferred by default.
0 commit comments