rewrite and update

Co-authored-by: Norbert Melzer <[email protected]>
Co-authored-by: Silvan Mosberger <[email protected]>

source/guides/faq.md

@@ -45,11 +45,11 @@ See <https://github.com/nix-community/home-manager>
 
 ### What's the recommended process for building custom packages?
 
-Please read [](packaging-existing-software).
+Please read [](packaging-tutorial).
 
 ### How to use a clone of the Nixpkgs repository to update or write new packages?
 
-Please read [](packaging-existing-software) and the [Nixpkgs contributing guide](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md).
+Please read [](packaging-tutorial) and the [Nixpkgs contributing guide](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md).
 
 ## NixOS
 
@@ -69,7 +69,7 @@ There are a few ways to resolve this mismatch in environment expectations:
   - Build from source.
 
     Many open-source programs are highly flexible at compile time in terms of where their files go.
-    For an introduction to this, see [](../tutorials/packaging-existing-software).
+    For an introduction to this, see [](packaging-tutorial).
   - Modify the program's [ELF header](https://en.wikipedia.org/wiki/Executable_and_Linkable_Format) to include paths to libraries using [`autoPatchelfHook`](https://nixos.org/manual/nixpkgs/stable/#setup-hook-autopatchelfhook).
 
     Do this if building from source isn't feasible.

source/guides/recipes/python-environment.md

@@ -105,7 +105,7 @@ Others can now use the same shell environment as long as they have [Nix installe
 
 ## Next steps
 
-- [](packaging-existing-software)
+- [](packaging-tutorial)
 - [](file-sets-tutorial)
 - [](automatic-direnv)
 - [](./dependency-management.md)

source/guides/recipes/sharing-dependencies.md

@@ -1,7 +1,7 @@
 (sharing-dependencies)=
 # Dependencies in the development shell
 
-When [packaging software in `default.nix`](packaging-existing-software), you'll want a [development environment in `shell.nix`](declarative-reproducible-envs) to enter it conveniently with `nix-shell` or [automatically with `direnv`](./direnv).
+When [packaging software in `default.nix`](packaging-tutorial), you'll want a [development environment in `shell.nix`](declarative-reproducible-envs) to enter it conveniently with `nix-shell` or [automatically with `direnv`](./direnv).
 
 How to share the package's dependencies in `default.nix` with the development environment in `shell.nix`?
 
@@ -109,4 +109,4 @@ $ nix-shell --pure
 - [](pinning-nixpkgs)
 - [](./direnv)
 - [](python-dev-environment)
-- [](packaging-existing-software)
+- [](packaging-tutorial)