![]() Security fixes are submitted in the same way as other changes and thus the same guidelines apply. Push your changes to your fork of nixpkgs.Rebase your branch against current master. If you have commits pkg-name: oh, forgot to insert whitespace: squash commits in this case. And do sudo nixos-rebuild test -I nixpkgs= -fast. You can add new module to your NixOS configuration file (usually it’s /etc/nixos/configuration.nix).If you installed your package with nix-env, you can run nix-env -e pkg-name where pkg-name is as reported by nix-env -q to uninstall it from your system.It will appear in the same directory where you did nix-build. nix-build -A pkg-attribute-name and check results in the folder result.If you don’t want to install pkg in you profile.Make sure it’s in pkgs/top-level/all-packages.nix.nixos/nginx: refactor config generation.For example nixos/doc/manual/release-notes/rl-2003.xml.Ĭheck for unnecessary whitespace with git diff -check before committing.įormat the commit in a following way: (pkg-name | nixos/): (from -> to | init at version | refactor | etc) If you removed pkgs or made some major NixOS changes, write about it in the release notes for the next stable release. Please avoid working directly on the master branch. Because you will receive packages from binary cache. That will help you to avoid additional local compilations. You can make branch from a commit of your local nixos-version. Read Manual (How to write packages for Nix).
0 Comments
Leave a Reply. |