nixpkgs/nixos
Jan Tojnar b794b3eedb nixos/gnome: Update default fonts
GNOME 48 switched to new Inter and Iosevka based Adwaita fonts:
067cb4b155
https://blogs.gnome.org/monster/introducing-adwaita-fonts/

The default fonts were last changed to Cantarell and Source Code Pro in GNOME 3.32:
965062de47

Source Sans was added alongside them in c99a666aac
but it does not seem to be needed nowadays.
The only relevant package mentioning it according is GNOME Recipes:
https://codesearch.debian.net/search?q=Source+Sans+-pkg%3Atexlive+-pkg%3Aopenjdk+-pkg%3Abootswatch+-pkg%3Aqt%28%5Cd-%29%3Fwebengine+-pkg%3Afirefox+-pkg%3Ar-cran+-pkg%3Ataskflow+-pkg%3Afonts-adobe-sourcesans+-path%3Asvg%24+-path%3A%2Fdoc%2F+-path%3A%2Fdocs%2F&literal=1

DejaVu fonts are meant as a generic fallback but they are already pulled in by `fonts.enableDefaultPackages` option.
2025-05-08 19:28:27 +02:00
..
doc/manual nixos/gnome: Update default fonts 2025-05-08 19:28:27 +02:00
lib nixos/systemd: clarify what enableStrictShellChecks checks (#401460) 2025-04-27 14:15:15 +02:00
maintainers cloudstack: add to image/images 2025-04-14 14:03:58 +02:00
modules nixos/gnome: Update default fonts 2025-05-08 19:28:27 +02:00
tests nixosTests: fix pure eval by setting system to null (#404284) 2025-05-08 12:26:55 +02:00
COPYING
default.nix
README.md nixos/README.md: relax the requirement of providing option defaults (#334509) 2025-01-15 11:10:46 +08:00
release-combined.nix Revert "ecryptfs: add test to release-combined.nix" 2025-03-22 19:54:13 +01:00
release-small.nix nixos/release-small: fix nesting on new acme tests 2025-02-26 10:50:20 +03:00
release.nix nixos/release: drop amazonImageAutomaticSize 2025-04-08 10:25:49 +02:00

NixOS

NixOS is a Linux distribution based on the purely functional package management system Nix. More information can be found at https://nixos.org/nixos and in the manual in doc/manual.

Testing changes

You can add new module to your NixOS configuration file (usually its /etc/nixos/configuration.nix). And do sudo nixos-rebuild test -I nixpkgs=<path to your local nixpkgs folder> --fast.

Commit conventions

  • Make sure you read about the commit conventions common to Nixpkgs as a whole.

  • Format the commit messages in the following way:

    nixos/(module): (init module | add setting | refactor | etc)
    
    (Motivation for change. Link to release notes. Additional information.)
    

    Examples:

    • nixos/hydra: add bazBaz option

      Dual baz behavior is needed to do foo.

    • nixos/nginx: refactor config generation

      The old config generation system used impure shell scripts and could break in specific circumstances (see #1234).

Reviewing contributions

When changing the bootloader installation process, extra care must be taken. Grub installations cannot be rolled back, hence changes may break peoples installations forever. For any non-trivial change to the bootloader please file a PR asking for review, especially from @edolstra.

Module updates

Module updates are submissions changing modules in some ways. These often contains changes to the options or introduce new options.

Reviewing process:

  • Ensure that the module maintainers are notified.
    • The continuous integration system will make GitHub notify users based on the submitted changes, but it can happen that it misses some of the package maintainers.
  • Ensure that the module tests, if any, are succeeding.
    • You may invoke OfBorg with @ofborg test <module> to build nixosTests.<module>
  • Ensure that the introduced options are correct.
    • Type should be appropriate (string related types differs in their merging capabilities, loaOf and string types are deprecated).
    • Description, default and example should be provided.
  • Ensure that option changes are backward compatible.
    • mkRenamedOptionModuleWith provides a way to make renamed option backward compatible.
    • Use lib.versionAtLeast config.system.stateVersion "24.05" on backward incompatible changes which may corrupt, change or update the state stored on existing setups.
  • Ensure that removed options are declared with mkRemovedOptionModule.
  • Ensure that changes that are not backward compatible are mentioned in release notes.
  • Ensure that documentations affected by the change is updated.

Sample template for a module update review is provided below.

##### Reviewed points

- [ ] changes are backward compatible
- [ ] removed options are declared with `mkRemovedOptionModule`
- [ ] changes that are not backward compatible are documented in release notes
- [ ] module tests succeed on ARCHITECTURE
- [ ] options types are appropriate
- [ ] options description is set
- [ ] options example is provided
- [ ] documentation affected by the changes is updated

##### Possible improvements

##### Comments

New modules

New modules submissions introduce a new module to NixOS.

Reviewing process:

  • Ensure that all file paths fit the guidelines.
  • Ensure that the module tests, if any, are succeeding.
  • Ensure that new module tests are added to the package passthru.tests.
  • Ensure that the introduced options are correct.
    • Type should be appropriate (string related types differs in their merging capabilities, loaOf and string types are deprecated).
    • Description, default and example should be provided.
      • Defaults may only be omitted if both:
        1. The user is required to set the default in order to properly use the service.
        2. The lack of a default does not break evaluation when the module is not enabled.
  • Ensure that module meta field is present
    • Maintainers should be declared in meta.maintainers.
    • Module documentation should be declared with meta.doc.
  • Ensure that the module respect other modules functionality.
    • For example, enabling a module should not open firewall ports by default.

Sample template for a new module review is provided below.

##### Reviewed points

- [ ] module path fits the guidelines
- [ ] module tests, if any, succeed on ARCHITECTURE
- [ ] module tests, if any, are added to package `passthru.tests`
- [ ] options have appropriate types
- [ ] options have default
- [ ] options have example
- [ ] options have descriptions
- [ ] No unneeded package is added to `environment.systemPackages`
- [ ] `meta.maintainers` is set
- [ ] module documentation is declared in `meta.doc`

##### Possible improvements

##### Comments