Unverified Commit f6155d36 authored by Silvan Mosberger's avatar Silvan Mosberger Committed by GitHub
Browse files

docs: Fix some links (#381845)

parents bea00e03 b72bbe66

pkgs/README.md

+3 −3
Original line number Diff line number Diff line
@@ -87,7 +87,7 @@ Now that this is out of the way. To add a package to Nixpkgs: 


   - XML::Simple, a Perl module: [`pkgs/top-level/perl-packages.nix`](top-level/perl-packages.nix) (search for the `XMLSimple` attribute). Most Perl modules are so simple to build that they are defined directly in `perl-packages.nix`; no need to make a separate file for them.



   - Adobe Reader: [`pkgs/applications/misc/adobe-reader/default.nix`](applications/misc/adobe-reader/default.nix). Shows how binary-only packages can be supported. In particular the [builder](applications/misc/adobe-reader/builder.sh) uses `patchelf` to set the RUNPATH and ELF interpreter of the executables so that the right libraries are found at runtime.

   - Adobe Reader: [`pkgs/applications/misc/adobe-reader/default.nix`](applications/misc/adobe-reader/default.nix). Shows how binary-only packages can be supported. In particular the `postFixup` phase uses `patchelf` to set the RUNPATH and ELF interpreter of the executables so that the right libraries are found at runtime.



   Some notes:
@@ -337,7 +337,7 @@ In Nixpkgs, there are generally three different names associated with a package: 


- The `pname` attribute of the derivation. This is what most users see, in particular when using `nix-env`.



- The attribute name used for the package in the [`pkgs/by-name` structure](./pkgs/by-name/README.md) or in [`all-packages.nix`](./pkgs/top-level/all-packages.nix), and when passing it as a dependency in recipes.

- The attribute name used for the package in the [`pkgs/by-name` structure](./by-name/README.md) or in [`all-packages.nix`](./top-level/all-packages.nix), and when passing it as a dependency in recipes.



- The filename for (the directory containing) the Nix expression.
@@ -729,7 +729,7 @@ $ nix-build -A phoronix-test-suite.tests 


Here are examples of package tests:



- [Jasmin compile test](development/compilers/jasmin/test-assemble-hello-world/default.nix)

- [Jasmin compile test](by-name/ja/jasmin/test-assemble-hello-world/default.nix)

- [Lobster compile test](development/compilers/lobster/test-can-run-hello-world.nix)

- [Spacy annotation test](development/python-modules/spacy/annotation-test/default.nix)

- [Libtorch test](development/libraries/science/math/libtorch/test/default.nix)

pkgs/by-name/README.md

+1 −1
Original line number Diff line number Diff line
@@ -85,7 +85,7 @@ though it is expected to still take some time to get done. 
If you're interested in helping out with this effort,

please see [this ticket](https://github.com/NixOS/nixpkgs-vet/issues/56).



Since [only PRs to packages in `pkgs/by-name` can be automatically merged](../../CONTRIBUTING.md#how-to-merge-pull-requests),

Since [only PRs to packages in `pkgs/by-name` can be automatically merged](../../CONTRIBUTING.md#how-to-merge-pull-requests-yourself),

if package maintainers would like to use this feature, they are welcome to migrate their packages to `pkgs/by-name`.

To lessen PR traffic, they're encouraged to also perform some more general maintenance on the package in the same PR,

though this is not required and must not be expected.