cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

pkgs/by-name: Add manual migration guidelines

Browse source 
Motivated from seeing people starting to migrate packages manually when
it shouldn't be necessary or done differently.
This commit is contained in:
Silvan Mosberger 2023-09-12 00:18:09 +02:00
parent 54bc9b45a3
commit e27e30204b
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
pkgs/by-name/README.md
View file

@ -72,6 +72,22 @@ libfoo = callPackage ../by-name/so/some-package/package.nix {
}; };
``` ```
## Manual migration guidelines
Most packages are still defined in `all-packages.nix` and the [category hierarchy](../README.md#category-hierarchy).
Please hold off migrating your maintained packages to this directory.
1. An automated migration for the majority of packages [is being worked on](https://github.com/NixOS/nixpkgs/pull/211832).
In order to save on contributor and reviewer time, packages should only be migrated manually afterwards if they couldn't be migrated automatically.
1. Manual migrations should only be lightly encouraged if the relevant code is being worked on anyways.
For example with a package update or refactoring.
1. Manual migrations should not remove definitions from `all-packages.nix` with custom arguments.
That is a backwards-incompatible change because it changes the `.override` interface.
Such packages may still be moved to `pkgs/by-name` however, while keeping the definition in `all-packages.nix`.
See also [changing implicit attribute defaults](#changing-implicit-attribute-defaults).
## Limitations ## Limitations
There's some limitations as to which packages can be defined using this structure: There's some limitations as to which packages can be defined using this structure: