+1
-1
doc/builders/fetchers.chapter.md
+1
-1
doc/builders/fetchers.chapter.md
···The main difference between `fetchurl` and `fetchzip` is in how they store the contents. `fetchurl` will store the unaltered contents of the URL within the Nix store. `fetchzip` on the other hand will decompress the archive for you, making files and directories directly accessible in the future. `fetchzip` can only be used with archives. Despite the name, `fetchzip` is not limited to .zip files and can also be used with any tarball.-`fetchpatch` works very similarly to `fetchurl` with the same arguments expected. It expects patch files as a source and and performs normalization on them before computing the checksum. For example it will remove comments or other unstable parts that are sometimes added by version control systems and can change over time.Other fetcher functions allow you to add source code directly from a VCS such as subversion or git. These are mostly straightforward nambes based on the name of the command used with the VCS system. Because they give you a working repository, they act most like `fetchzip`.
···The main difference between `fetchurl` and `fetchzip` is in how they store the contents. `fetchurl` will store the unaltered contents of the URL within the Nix store. `fetchzip` on the other hand will decompress the archive for you, making files and directories directly accessible in the future. `fetchzip` can only be used with archives. Despite the name, `fetchzip` is not limited to .zip files and can also be used with any tarball.+`fetchpatch` works very similarly to `fetchurl` with the same arguments expected. It expects patch files as a source and performs normalization on them before computing the checksum. For example it will remove comments or other unstable parts that are sometimes added by version control systems and can change over time.Other fetcher functions allow you to add source code directly from a VCS such as subversion or git. These are mostly straightforward nambes based on the name of the command used with the VCS system. Because they give you a working repository, they act most like `fetchzip`.
+1
-1
doc/builders/images/snaptools.xml
+1
-1
doc/builders/images/snaptools.xml
+1
-1
doc/languages-frameworks/android.section.md
+1
-1
doc/languages-frameworks/android.section.md
···
···
+1
-1
doc/languages-frameworks/dotnet.section.md
+1
-1
doc/languages-frameworks/dotnet.section.md
···The `dotnetCorePackages.sdk_X_Y` is preferred over the old dotnet-sdk as both major and minor version are very important for a dotnet environment. If a given minor version isn't present (or was changed), then this will likely break your ability to build a project.-## dotnetCorePackages.sdk vs vs dotnetCorePackages.net vs dotnetCorePackages.netcore vs dotnetCorePackages.aspnetcoreThe `dotnetCorePackages.sdk` contains both a runtime and the full sdk of a given version. The `net`, `netcore` and `aspnetcore` packages are meant to serve as minimal runtimes to deploy alongside already built applications. For runtime versions >= .NET 5 `net` is used while `netcore` is used for older .NET Core runtime version.
···The `dotnetCorePackages.sdk_X_Y` is preferred over the old dotnet-sdk as both major and minor version are very important for a dotnet environment. If a given minor version isn't present (or was changed), then this will likely break your ability to build a project.+## dotnetCorePackages.sdk vs dotnetCorePackages.net vs dotnetCorePackages.netcore vs dotnetCorePackages.aspnetcoreThe `dotnetCorePackages.sdk` contains both a runtime and the full sdk of a given version. The `net`, `netcore` and `aspnetcore` packages are meant to serve as minimal runtimes to deploy alongside already built applications. For runtime versions >= .NET 5 `net` is used while `netcore` is used for older .NET Core runtime version.
+2
-2
doc/languages-frameworks/lua.section.md
+2
-2
doc/languages-frameworks/lua.section.md
······[luarocks2nix](https://github.com/nix-community/luarocks) is a tool capable of generating nix derivations from both rockspec and src.rock (and favors the src.rock).-For instance if the rockspec defines `external_dependencies`, these need to be manually added in in its rockspec file then it won't work.You can try converting luarocks packages to nix packages with the command `nix-shell -p luarocks-nix` and then `luarocks nix PKG_NAME`.
······[luarocks2nix](https://github.com/nix-community/luarocks) is a tool capable of generating nix derivations from both rockspec and src.rock (and favors the src.rock).+For instance if the rockspec defines `external_dependencies`, these need to be manually added in its rockspec file then it won't work.You can try converting luarocks packages to nix packages with the command `nix-shell -p luarocks-nix` and then `luarocks nix PKG_NAME`.
+2
-2
doc/languages-frameworks/python.section.md
+2
-2
doc/languages-frameworks/python.section.md
······
······
+1
-1
doc/languages-frameworks/ruby.section.md
+1
-1
doc/languages-frameworks/ruby.section.md
···If you want to package a specific version, you can use the standard Gemfile syntax for that, e.g. `gem 'mdl', '0.5.0'`, but if you want the latest stable version anyway, it's easier to update by simply running the `bundle lock` and `bundix` steps again.
···If you want to package a specific version, you can use the standard Gemfile syntax for that, e.g. `gem 'mdl', '0.5.0'`, but if you want the latest stable version anyway, it's easier to update by simply running the `bundle lock` and `bundix` steps again.
+1
-1
doc/languages-frameworks/rust.section.md
+1
-1
doc/languages-frameworks/rust.section.md
+1
-1
doc/using/overlays.xml
+1
-1
doc/using/overlays.xml
···-For BLAS/LAPACK switching to work correctly, all packages must depend on <literal>blas</literal> or <literal>lapack</literal>. This ensures that only one BLAS/LAPACK library is used at one time. There are two versions versions of BLAS/LAPACK currently in the wild, <literal>LP64</literal> (integer size = 32 bits) and <literal>ILP64</literal> (integer size = 64 bits). Some software needs special flags or patches to work with <literal>ILP64</literal>. You can check if <literal>ILP64</literal> is used in Nixpkgs with <varname>blas.isILP64</varname> and <varname>lapack.isILP64</varname>. Some software does NOT work with <literal>ILP64</literal>, and derivations need to specify an assertion to prevent this. You can prevent <literal>ILP64</literal> from being used with the following:
···+For BLAS/LAPACK switching to work correctly, all packages must depend on <literal>blas</literal> or <literal>lapack</literal>. This ensures that only one BLAS/LAPACK library is used at one time. There are two versions of BLAS/LAPACK currently in the wild, <literal>LP64</literal> (integer size = 32 bits) and <literal>ILP64</literal> (integer size = 64 bits). Some software needs special flags or patches to work with <literal>ILP64</literal>. You can check if <literal>ILP64</literal> is used in Nixpkgs with <varname>blas.isILP64</varname> and <varname>lapack.isILP64</varname>. Some software does NOT work with <literal>ILP64</literal>, and derivations need to specify an assertion to prevent this. You can prevent <literal>ILP64</literal> from being used with the following:
+13
pkgs/applications/backup/pika-backup/borg-path.patch
+13
pkgs/applications/backup/pika-backup/borg-path.patch
···
···
+77
pkgs/applications/backup/pika-backup/default.nix
+77
pkgs/applications/backup/pika-backup/default.nix
···
···
+2
-2
pkgs/applications/misc/worker/default.nix
+2
-2
pkgs/applications/misc/worker/default.nix
+2
pkgs/applications/networking/browsers/firefox-bin/default.nix
+2
pkgs/applications/networking/browsers/firefox-bin/default.nix
+2
-2
pkgs/applications/video/qstopmotion/default.nix
+2
-2
pkgs/applications/video/qstopmotion/default.nix
···url = "mirror://sourceforge/project/${pname}/Version_${builtins.replaceStrings ["."] ["_"] version}/${pname}-${version}-Source.tar.gz";
···url = "mirror://sourceforge/project/${pname}/Version_${builtins.replaceStrings ["."] ["_"] version}/${pname}-${version}-Source.tar.gz";
+2
-2
pkgs/development/compilers/go/1.15.nix
+2
-2
pkgs/development/compilers/go/1.15.nix
······
······
+2
-2
pkgs/development/compilers/go/1.16.nix
+2
-2
pkgs/development/compilers/go/1.16.nix
······
······
+3
-3
pkgs/development/tools/wrangler/default.nix
+3
-3
pkgs/development/tools/wrangler/default.nix
···
···
+2
-2
pkgs/development/web/insomnia/default.nix
+2
-2
pkgs/development/web/insomnia/default.nix
···"https://github.com/Kong/insomnia/releases/download/core%40${version}/Insomnia.Core-${version}.deb";
···"https://github.com/Kong/insomnia/releases/download/core%40${version}/Insomnia.Core-${version}.deb";
+1
-1
pkgs/os-specific/linux/firmware/firmware-linux-nonfree/default.nix
+1
-1
pkgs/os-specific/linux/firmware/firmware-linux-nonfree/default.nix
+3
-3
pkgs/servers/imgproxy/default.nix
+3
-3
pkgs/servers/imgproxy/default.nix
···
···
+2
-2
pkgs/servers/nats-streaming-server/default.nix
+2
-2
pkgs/servers/nats-streaming-server/default.nix
···
···
+3
-3
pkgs/tools/admin/procs/default.nix
+3
-3
pkgs/tools/admin/procs/default.nix
···
···
+2
-2
pkgs/tools/filesystems/catcli/default.nix
+2
-2
pkgs/tools/filesystems/catcli/default.nix
···
···
+2
-2
pkgs/tools/misc/units/default.nix
+2
-2
pkgs/tools/misc/units/default.nix
+21
-18
pkgs/tools/networking/boundary/default.nix
+21
-18
pkgs/tools/networking/boundary/default.nix
···
···
+2
-2
pkgs/tools/system/snooze/default.nix
+2
-2
pkgs/tools/system/snooze/default.nix
···
···
+2
pkgs/top-level/all-packages.nix
+2
pkgs/top-level/all-packages.nix
···pidgin-window-merge = callPackage ../applications/networking/instant-messengers/pidgin-plugins/window-merge { };purple-discord = callPackage ../applications/networking/instant-messengers/pidgin-plugins/purple-discord { };purple-hangouts = callPackage ../applications/networking/instant-messengers/pidgin-plugins/purple-hangouts { };
···pidgin-window-merge = callPackage ../applications/networking/instant-messengers/pidgin-plugins/window-merge { };purple-discord = callPackage ../applications/networking/instant-messengers/pidgin-plugins/purple-discord { };purple-hangouts = callPackage ../applications/networking/instant-messengers/pidgin-plugins/purple-hangouts { };