treewide: fix typos
done with `fd \\\.md$ . --type f -x typos --write-changes`
This commit is contained in:
Peder Bergebakken Sundt
parent
63d0ef62b7
commit
d525eb5838
@ -9,7 +9,7 @@ Build helpers don't always support fixed-point arguments yet, as support in [`st
|
||||
|
||||
Developers can use the Nixpkgs library function [`lib.customisation.extendMkDerivation`](#function-library-lib.customisation.extendMkDerivation) to define a build helper supporting fixed-point arguments from an existing one with such support, with an attribute overlay similar to the one taken by [`<pkg>.overrideAttrs`](#sec-pkg-overrideAttrs).
|
||||
|
||||
Beside overriding, `lib.extendMkDerivation` also supports `excludeDrvArgNames` to optionally exclude some arguments in the input fixed-point argumnts from passing down the base build helper (specified as `constructDrv`).
|
||||
Beside overriding, `lib.extendMkDerivation` also supports `excludeDrvArgNames` to optionally exclude some arguments in the input fixed-point arguments from passing down the base build helper (specified as `constructDrv`).
|
||||
|
||||
:::{.example #ex-build-helpers-extendMkDerivation}
|
||||
|
||||
|
||||
@ -304,4 +304,4 @@ In case a project doesn't have external dependencies or dependencies are vendore
|
||||
- Run `go mod init <module name>` in `postPatch`
|
||||
|
||||
In case the package has external dependencies that aren't vendored or the build setup is more complex the upstream source might need to be patched.
|
||||
Examples for the migration can be found in the [issue tracking migration withing nixpkgs](https://github.com/NixOS/nixpkgs/issues/318069).
|
||||
Examples for the migration can be found in the [issue tracking migration within nixpkgs](https://github.com/NixOS/nixpkgs/issues/318069).
|
||||
|
||||
@ -11,7 +11,7 @@ See the next section for more details.
|
||||
|
||||
## Custom configuration {#neovim-custom-configuration}
|
||||
|
||||
There are two wrappers available to provide additionnal configuration around the vanilla package `pkgs.neovim-unwrapped`:
|
||||
There are two wrappers available to provide additional configuration around the vanilla package `pkgs.neovim-unwrapped`:
|
||||
1. `wrapNeovim`: the historical one you should use
|
||||
2. `wrapNeovimUnstable` intended to replace the former. It has more features but
|
||||
the interface is not stable yet.
|
||||
@ -112,7 +112,7 @@ upload their package to [](www.luarocks.org). This means less work for nixpkgs m
|
||||
This means several neovim plugins are first packaged as nixpkgs [lua
|
||||
packages](#packaging-a-library-on-luarocks), and converted via `buildNeovimPlugin` in
|
||||
a vim plugin. This conversion is necessary because neovim expects lua folders to be
|
||||
top-level while luarocks installs them in varous subfolders by default.
|
||||
top-level while luarocks installs them in various subfolders by default.
|
||||
|
||||
For instance:
|
||||
```nix
|
||||
|
||||
@ -44,7 +44,7 @@
|
||||
|
||||
- Structure of the `functor` of some types has changed. `functor` is an implementation detail and should not be relied upon. If you did rely on it let us know in this [PR](https://github.com/NixOS/nixpkgs/pull/363565).
|
||||
- [`lib.types.enum`](https://nixos.org/manual/nixos/unstable/#sec-option-types-basic): Previously the `functor.payload` was the list of enum values directly. Now it is an attribute set containing the values in the `values` attribute.
|
||||
- [`lib.types.separatedString`](https://nixos.org/manual/nixos/unstable/#sec-option-types-string): Previously the `functor.payload` was the seperator directly. Now it is an attribute set containing the seperator in the `sep` attribute.
|
||||
- [`lib.types.separatedString`](https://nixos.org/manual/nixos/unstable/#sec-option-types-string): Previously the `functor.payload` was the separator directly. Now it is an attribute set containing the separator in the `sep` attribute.
|
||||
|
||||
- The `tinycc` package now has the `dev`, `doc` and `lib` outputs, thus,
|
||||
`tinycc.out` may now only provide the tcc and cross compilers binaries.
|
||||
|
||||
@ -191,8 +191,8 @@ have a predefined type and string generator already declared under
|
||||
in {
|
||||
a = 1;
|
||||
b = format.lib.mkSubstitution "a";
|
||||
c = format.lib.mkSubstition "SOME_ENVVAR";
|
||||
d = format.lib.mkSubstition {
|
||||
c = format.lib.mkSubstitution "SOME_ENVVAR";
|
||||
d = format.lib.mkSubstitution {
|
||||
value = "SOME_OPTIONAL_ENVVAR";
|
||||
optional = true;
|
||||
};
|
||||
@ -333,7 +333,7 @@ have a predefined type and string generator already declared under
|
||||
`{ sections = {}; globalSection = {}; }` where *sections* are several
|
||||
sections as with *pkgs.formats.ini* and *globalSection* being just a single
|
||||
attrset of key-value pairs for a single section, the global section which
|
||||
preceedes the section definitions.
|
||||
precedes the section definitions.
|
||||
|
||||
The attribute `lib.type.atom` contains the used INI atom.
|
||||
|
||||
|
||||
@ -409,7 +409,7 @@ In addition to numerous new and upgraded packages, this release has the followin
|
||||
configuration file. For details, see the [upstream changelog](https://github.com/DataDog/datadog-agent/blob/main/CHANGELOG.rst).
|
||||
|
||||
- `opencv2` no longer includes the non-free libraries by default, and consequently `pfstools` no longer includes OpenCV support by default. Both packages now support an `enableUnfree` option to re-enable this functionality.
|
||||
- `services.xserver.displayManager.defaultSession = "plasma5"` does not work anymore, instead use either `"plasma"` for the Plasma X11 session or `"plasmawayland"` for the Plasma Wayland sesison.
|
||||
- `services.xserver.displayManager.defaultSession = "plasma5"` does not work anymore, instead use either `"plasma"` for the Plasma X11 session or `"plasmawayland"` for the Plasma Wayland session.
|
||||
|
||||
- `boot.kernelParams` now only accepts one command line parameter per string. This change is aimed to reduce common mistakes like "param = 12", which would be parsed as 3 parameters.
|
||||
|
||||
|
||||
@ -472,7 +472,7 @@ Make sure to also check the many updates in the [Nixpkgs library](#sec-release-2
|
||||
- `pharo` has been updated to latest stable v10.0.8, which is compatible with
|
||||
the latest stable and oldstable images (Pharo 10 and 11). The VM in question
|
||||
is the 64bit Spur. The 32bit version has been dropped due to lack of
|
||||
maintenance. The Cog VM has been deleted because it is severily outdated.
|
||||
maintenance. The Cog VM has been deleted because it is severely outdated.
|
||||
Finally, the `pharo-launcher` package has been deleted because it was not
|
||||
compatible with the newer VM, and due to lack of maintenance.
|
||||
|
||||
|
||||
@ -173,7 +173,7 @@ The pre-existing `services.ankisyncd` has been marked deprecated and will be dro
|
||||
|
||||
- [ryzen-monitor-ng](https://github.com/mann1x/ryzen_monitor_ng), a desktop AMD CPU power monitor and controller, similar to Ryzen Master but for Linux. Available as [programs.ryzen-monitor-ng](#opt-programs.ryzen-monitor-ng.enable).
|
||||
|
||||
- [ryzen-smu](https://gitlab.com/leogx9r/ryzen_smu), Linux kernel driver to expose the SMU (System Management Unit) for certain AMD Ryzen Processors. Includes the userspace program `monitor_cpu`. Available at [hardward.cpu.amd.ryzen-smu](#opt-hardware.cpu.amd.ryzen-smu.enable).
|
||||
- [ryzen-smu](https://gitlab.com/leogx9r/ryzen_smu), Linux kernel driver to expose the SMU (System Management Unit) for certain AMD Ryzen Processors. Includes the userspace program `monitor_cpu`. Available at [hardware.cpu.amd.ryzen-smu](#opt-hardware.cpu.amd.ryzen-smu.enable).
|
||||
|
||||
- [Scrutiny](https://github.com/AnalogJ/scrutiny), a S.M.A.R.T monitoring tool for hard disks with a web frontend. Available as [services.scrutiny](#opt-services.scrutiny.enable).
|
||||
|
||||
|
||||
@ -303,7 +303,7 @@
|
||||
|
||||
- `tldr` now uses [`tldr-python-client`](https://github.com/tldr-pages/tldr-python-client) instead of [`tldr-c-client`](https://github.com/tldr-pages/tldr-c-client) which is unmaintained.
|
||||
|
||||
- `services.bird2` has been renamed to `services.bird` and the default bird package has been switched to `bird3`. `bird2` can still be choosen via the `services.bird.package` option.
|
||||
- `services.bird2` has been renamed to `services.bird` and the default bird package has been switched to `bird3`. `bird2` can still be chosen via the `services.bird.package` option.
|
||||
|
||||
- `renovate` was updated to v39. See the [upstream release notes](https://docs.renovatebot.com/release-notes-for-major-versions/#version-39) for breaking changes.
|
||||
Like upstream's docker images, renovate now runs on NodeJS 22.
|
||||
@ -389,9 +389,9 @@
|
||||
|
||||
- `matomo` now defaults to version 5 (previously available as `matomo_5`). Version 4 has been removed as it reached EOL on December 19, 2024.
|
||||
|
||||
- `matomo-beta` has been removed as the version of the `matomo` package can now be easily overriden through `overrideAttrs` (see [PR #374022](https://github.com/NixOS/nixpkgs/pull/374022))
|
||||
- `matomo-beta` has been removed as the version of the `matomo` package can now be easily overridden through `overrideAttrs` (see [PR #374022](https://github.com/NixOS/nixpkgs/pull/374022))
|
||||
|
||||
- `docker_24` has been removed, as it was EOL with vulnerabilites since June 08, 2024.
|
||||
- `docker_24` has been removed, as it was EOL with vulnerabilities since June 08, 2024.
|
||||
|
||||
- `containerd` has been updated to v2, which contains breaking changes. See the [containerd
|
||||
2.0](https://github.com/containerd/containerd/blob/main/docs/containerd-2.0.md) documentation for more
|
||||
@ -447,7 +447,7 @@
|
||||
- `zf` was updated to 0.10.2, which includes breaking changes from the [0.10.0 release](https://github.com/natecraddock/zf/releases/tag/0.10.0).
|
||||
`zf` no longer does Unicode normalization of the input and no longer supports terminal escape sequences in the `ZF_PROMPT` environment variable.
|
||||
|
||||
- `programs.clash-verge.tunMode` was deprecated and removed because now service mode is neccessary to start program. Without `programs.clash-verge.enable`, clash-verge-rev will refuse to start.
|
||||
- `programs.clash-verge.tunMode` was deprecated and removed because now service mode is necessary to start program. Without `programs.clash-verge.enable`, clash-verge-rev will refuse to start.
|
||||
|
||||
- `siduck76-st` has been renamed to `st-snazzy`, like the project's [flake](https://github.com/siduck/st/blob/main/flake.nix).
|
||||
|
||||
|
||||
@ -256,7 +256,7 @@ PostgreSQL's versioning policy is described [here](https://www.postgresql.org/su
|
||||
- After that a version is considered end-of-life (EOL).
|
||||
- Around February each year is the first time an EOL-release will not have received regular updates anymore.
|
||||
|
||||
Technically, we'd not want to have EOL'ed packages in a stable NixOS release, which is to be supported until one month after the previous release. Thus, with NixOS' release schedule in May and November, the oldest PostgreSQL version in nixpkgs would have to be supported until December. It could be argued that a soon-to-be-EOL-ed version should thus be removed in May for the .05 release already. But since new security vulnerabilities are first disclosed in Februrary of the following year, we agreed on keeping the oldest PostgreSQL major version around one more cycle in [#310580](https://github.com/NixOS/nixpkgs/pull/310580#discussion_r1597284693).
|
||||
Technically, we'd not want to have EOL'ed packages in a stable NixOS release, which is to be supported until one month after the previous release. Thus, with NixOS' release schedule in May and November, the oldest PostgreSQL version in nixpkgs would have to be supported until December. It could be argued that a soon-to-be-EOL-ed version should thus be removed in May for the .05 release already. But since new security vulnerabilities are first disclosed in February of the following year, we agreed on keeping the oldest PostgreSQL major version around one more cycle in [#310580](https://github.com/NixOS/nixpkgs/pull/310580#discussion_r1597284693).
|
||||
|
||||
Thus:
|
||||
- In September/October the new major version will be released and added to nixos-unstable.
|
||||
@ -374,7 +374,7 @@ several common hardening options from `systemd`, most notably:
|
||||
* A system call filter (see {manpage}`systemd.exec(5)` for details on `@system-service`).
|
||||
* A stricter default UMask (`0027`).
|
||||
* Only sockets of type `AF_INET`/`AF_INET6`/`AF_NETLINK`/`AF_UNIX` allowed.
|
||||
* Restricted filesystem access (private `/tmp`, most of the file-system hierachy is mounted read-only, only process directories in `/proc` that are owned by the same user).
|
||||
* Restricted filesystem access (private `/tmp`, most of the file-system hierarchy is mounted read-only, only process directories in `/proc` that are owned by the same user).
|
||||
* When using [`TABLESPACE`](https://www.postgresql.org/docs/current/manage-ag-tablespaces.html)s, make sure to add the filesystem paths to `ReadWritePaths` like this:
|
||||
```nix
|
||||
{
|
||||
|
||||
@ -174,7 +174,7 @@ To prevent this, set `validate = false` or omit the `[upstream.options]`.
|
||||
|
||||
### API {#module-services-crab-hole-api}
|
||||
The API allows a user to fetch statistic and information about the crab-hole instance.
|
||||
Basic information is availablee for everyone, while more detailed information is secured by a key, which will be set with the `admin_key` option.
|
||||
Basic information is available for everyone, while more detailed information is secured by a key, which will be set with the `admin_key` option.
|
||||
|
||||
```nix
|
||||
{
|
||||
@ -190,7 +190,7 @@ Basic information is availablee for everyone, while more detailed information is
|
||||
|
||||
```
|
||||
|
||||
The documentation can be enabled seperately for the instance with `show_doc`.
|
||||
The documentation can be enabled separately for the instance with `show_doc`.
|
||||
This will then create an additional webserver, which hosts the API documentation.
|
||||
An additional resource is in work in the [crab-hole repository](https://github.com/LuckyTurtleDev/crab-hole).
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ Here is a basic configuration:
|
||||
|
||||
## Reverse proxy configuration {#module-services-pingvin-share-reverse-proxy-configuration}
|
||||
|
||||
The prefered method to run this service is behind a reverse proxy not to expose an open port. This, you can configure Nginx such like this:
|
||||
The preferred method to run this service is behind a reverse proxy not to expose an open port. This, you can configure Nginx such like this:
|
||||
|
||||
```nix
|
||||
{
|
||||
|
||||
@ -18,7 +18,7 @@ To test the build process of every IDE (as well as the process for adding plugin
|
||||
- Run ./bin/update_bin.py, this will update binary IDEs and plugins, and automatically commit them
|
||||
- Source builds need a bit more effort, as they **aren't automated at the moment**:
|
||||
- Find the build of the stable release you want to target (usually different for pycharm and idea, should have three components)
|
||||
- Build number is avaliable on JetBrains website:
|
||||
- Build number is available on JetBrains website:
|
||||
- IDEA: https://www.jetbrains.com/idea/download/other.html
|
||||
- PyCharm: https://www.jetbrains.com/pycharm/download/other.html
|
||||
- Update the `version` & `buildNumber` fields in source/ides.json
|
||||
|
||||
@ -61,7 +61,7 @@ Here's an overview of this mapping:
|
||||
|
||||
- The keys of this mapping _must_ be an exhaustive list of all identifiers in the source files.
|
||||
- The first element of the value of this mapping _must_ be the current output location (path and anchor) of the content signified by the identifier in the mapping key.
|
||||
- While the order of the remaining elements is unconstrained, please only prepend to this list when the content under the indentifier moves in order to keep the diffs readable.
|
||||
- While the order of the remaining elements is unconstrained, please only prepend to this list when the content under the identifier moves in order to keep the diffs readable.
|
||||
|
||||
In case this identifier is renamed, the mapping would change into:
|
||||
|
||||
|
||||
@ -1 +1 @@
|
||||
`textlint-rule-common-misspellings` is an old and mature libary.
|
||||
`textlint-rule-common-misspellings` is an old and mature library.
|
||||
|
||||
@ -76,7 +76,7 @@ There shouldn't be a need to disable this hook, but you can set
|
||||
### Too narrow version constraints
|
||||
|
||||
Every once in a while a dependency constraint is more narrow than it
|
||||
needs to be. Instead of applying brittle substitions the version constraint
|
||||
needs to be. Instead of applying brittle substitutions the version constraint
|
||||
can be ignored on a per requirement basis.
|
||||
|
||||
```nix
|
||||
|
||||
Loading…
Reference in New Issue
Block a user