git.iko.soy/typeable/nixpkgs
on master help sign in
Remove repeating words from doc
commit3329093c6aca716761a3d91089d49e5cbb873d77 authorFlorian Engel <florianengel39@gmail.com> dateSun 14 Mar 2021, 11:49 (6 years ago) parenta58bd74
9 files changed+11−11
doc/builders/fetchers.chapter.md+1−1 doc/builders/images/snaptools.xml+1−1 doc/languages-frameworks/android.section.md+1−1 doc/languages-frameworks/dotnet.section.md+1−1 doc/languages-frameworks/lua.section.md+2−2 doc/languages-frameworks/python.section.md+2−2 doc/languages-frameworks/ruby.section.md+1−1 doc/languages-frameworks/rust.section.md+1−1 doc/using/overlays.xml+1−1
doc/builders/fetchers.chapter.md+1−1
@@ -18,7 +18,7 @@ stdenv.mkDerivation {
1818
1919The 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.
2020
21−`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.
21+`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.
2222
2323
2424Other 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`.
doc/builders/images/snaptools.xml+1−1
@@ -16,7 +16,7 @@
1616 </para>
1717
1818 <para>
19− The <parameter>base</parameter> should not be be specified, as <function>makeSnap</function> will force set it.
19+ The <parameter>base</parameter> should not be specified, as <function>makeSnap</function> will force set it.
2020 </para>
2121
2222 <para>
doc/languages-frameworks/android.section.md+1−1
@@ -80,7 +80,7 @@ Most of the function arguments have reasonable default settings.
8080
8181You can specify license names:
8282
83−* `extraLicenses` is a list of of license names.
83+* `extraLicenses` is a list of license names.
8484 You can get these names from repo.json or `querypackages.sh licenses`. The SDK
8585 license (`android-sdk-license`) is accepted for you if you set accept_license
8686 to true. If you are doing something like working with preview SDKs, you will
doc/languages-frameworks/dotnet.section.md+1−1
@@ -64,7 +64,7 @@ $ dotnet --info
6464
6565The `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.
6666
67−## dotnetCorePackages.sdk vs vs dotnetCorePackages.net vs dotnetCorePackages.netcore vs dotnetCorePackages.aspnetcore
67+## dotnetCorePackages.sdk vs dotnetCorePackages.net vs dotnetCorePackages.netcore vs dotnetCorePackages.aspnetcore
6868
6969The `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.
7070
doc/languages-frameworks/lua.section.md+2−2
@@ -50,7 +50,7 @@ and install it in your profile with
5050```shell
5151nix-env -iA nixpkgs.myLuaEnv
5252```
53−The environment is is installed by referring to the attribute, and considering
53+The environment is installed by referring to the attribute, and considering
5454the `nixpkgs` channel was used.
5555
5656#### Lua environment defined in `/etc/nixos/configuration.nix`
@@ -129,7 +129,7 @@ the whitelist maintainers/scripts/luarocks-packages.csv and updated by running m
129129[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).
130130The automation only goes so far though and some packages need to be customized.
131131These customizations go in `pkgs/development/lua-modules/overrides.nix`.
132−For instance if the rockspec defines `external_dependencies`, these need to be manually added in in its rockspec file then it won't work.
132+For instance if the rockspec defines `external_dependencies`, these need to be manually added in its rockspec file then it won't work.
133133
134134You can try converting luarocks packages to nix packages with the command `nix-shell -p luarocks-nix` and then `luarocks nix PKG_NAME`.
135135Nix rely on luarocks to install lua packages, basically it runs:
doc/languages-frameworks/python.section.md+2−2
@@ -334,7 +334,7 @@ Above, we were mostly just focused on use cases and what to do to get started
334334creating working Python environments in nix.
335335
336336Now that you know the basics to be up and running, it is time to take a step
337−back and take a deeper look at at how Python packages are packaged on Nix. Then,
337+back and take a deeper look at how Python packages are packaged on Nix. Then,
338338we will look at how you can use development mode with your code.
339339
340340#### Python library packages in Nixpkgs
@@ -918,7 +918,7 @@ because their behaviour is different:
918918
919919* `nativeBuildInputs ? []`: Build-time only dependencies. Typically executables
920920 as well as the items listed in `setup_requires`.
921−* `buildInputs ? []`: Build and/or run-time dependencies that need to be be
921+* `buildInputs ? []`: Build and/or run-time dependencies that need to be
922922 compiled for the host machine. Typically non-Python libraries which are being
923923 linked.
924924* `checkInputs ? []`: Dependencies needed for running the `checkPhase`. These
doc/languages-frameworks/ruby.section.md+1−1
@@ -229,7 +229,7 @@ end
229229
230230If 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.
231231
232−Now you can also also make a `default.nix` that looks like this:
232+Now you can also make a `default.nix` that looks like this:
233233
234234```nix
235235{ bundlerApp }:
doc/languages-frameworks/rust.section.md+1−1
@@ -737,7 +737,7 @@ with import "${src.out}/rust-overlay.nix" pkgs pkgs;
737737stdenv.mkDerivation {
738738 name = "rust-env";
739739 buildInputs = [
740− # Note: to use use stable, just replace `nightly` with `stable`
740+ # Note: to use stable, just replace `nightly` with `stable`
741741 latest.rustChannels.nightly.rust
742742
743743 # Add some extra dependencies from `pkgs`
doc/using/overlays.xml+1−1
@@ -230,7 +230,7 @@ self: super:
230230 </para>
231231
232232 <para>
233− 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:
233+ 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:
234234 </para>
235235
236236<programlisting>