jalil/configuration.nix
1
1
Fork 0
Code Issues 2 Pull requests 2 Projects Activity Actions

wip: niri take 2 [skip-ci] #357

Draft
jalil wants to merge 1 commit from push-xstqnkxmwxvm into main
pull from: push-xstqnkxmwxvm
merge into: jalil:main
Conversation 1 Commits 1 Files changed 3 +74
jalil commented 2025-03-16 22:33:56 +01:00
Owner
Copy link

Take two, since one wasn't enough.

Take two, since one wasn't enough.
jalil self-assigned this 2025-03-16 22:33:56 +01:00
jalil added 1 commit 2025-03-16 22:33:56 +01:00
wip: niri take 2 [skip-ci]
Some checks failed
/ check (push) Successful in 8s
Details
/ check-renovaterc (push) Successful in 3s
Details
/ build-packages (push) Successful in 13s
Details
/ build-vm (push) Failing after 26s
Details
/ report-size (push) Successful in 1m2s
Details
885fc0e462 
Take two, since one wasn't enough.
forgejo-actions commented 2025-03-16 22:35:15 +01:00
First-time contributor
Copy link

Flake output sizes

Definitions
  • Name: the name of the package/configuration.
  • Size: the closure size (size on disk/NAR size + all transitive dependencies).
  • NAR Size: the size of the build output (package without the dependencies).
  • [NAR] Size Change: the amount changed compared to the main branch.
Tips on reading this data
  • For NixOS configurations you generally care only about the Size (closure size/size on disk).
    • Reduce the Size by disabling unneeded services/default packages.
  • For Packages you care about both the Size and the NAR Size.
    • Reduce the NAR Size by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc.
    • Reduce the Size by reducing the dependencies (e.g. buildInputs).
    • Don't worry too much about size, some dependencies are deduplicated, e.g. glibc adds ~40MiB to the Size, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. musl is not gonna improve things.

NixOS Configurations

Name Size Size Change NAR Size NAR Size Change
vm 9.0GiB 9.0GiB 19KiB 19KiB

Packages

Name Size Size Change NAR Size NAR Size Change
audiomenu 42MiB 0B 1.4MiB 0B
docs 2.4MiB 0B 2.4MiB 0B
docs-home-markdown 11KiB 0B 11KiB 0B
docs-nixos-markdown 6.5KiB 0B 6.5KiB 0B
docs-nvim-markdown 2.4KiB 0B 2.4KiB 0B
jpassmenu 43MiB 0B 2.3MiB 0B
nvim 1.4GiB 0B 578KiB 0B
nvim-headless 389MiB 0B 578KiB 0B
nvim-no-lsps 1.1GiB 0B 578KiB 0B
nvim-no-ts 1.5GiB 0B 578KiB 0B
nvim-small 929MiB 0B 578KiB 0B
<!-- AUTOGENERATED by nix-flake-outputs-size action --> ## Flake output sizes <details><summary><b>Definitions</b></summary> - `Name`: the name of the package/configuration. - `Size`: the closure size (size on disk/NAR size + all transitive dependencies). - `NAR Size`: the size of the build output (package without the dependencies). - `[NAR] Size Change`: the amount changed compared to the main branch. </details> <details><summary><b>Tips on reading this data</b></summary> - For NixOS configurations you generally care only about the `Size` (closure size/size on disk). - Reduce the `Size` by disabling unneeded services/default packages. - For Packages you care about both the `Size` and the `NAR Size`. - Reduce the `NAR Size` by reducing the size of the build outputs, e.g. don't copy unnecessary data to the $out dir, optimize binaries for size, etc. - Reduce the `Size` by reducing the dependencies (e.g. `buildInputs`). - Don't worry too much about size, some dependencies are deduplicated, e.g. `glibc` adds ~40MiB to the `Size`, but is generally shared by ~every binary on the system, so, chances are, you are already including it from somewhere else and statically linking with e.g. `musl` is not gonna improve things. </details> ## NixOS Configurations | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `vm` | 9.0GiB | 9.0GiB | 19KiB | 19KiB | ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `audiomenu` | 42MiB | 0B | 1.4MiB | 0B | | `docs` | 2.4MiB | 0B | 2.4MiB | 0B | | `docs-home-markdown` | 11KiB | 0B | 11KiB | 0B | | `docs-nixos-markdown` | 6.5KiB | 0B | 6.5KiB | 0B | | `docs-nvim-markdown` | 2.4KiB | 0B | 2.4KiB | 0B | | `jpassmenu` | 43MiB | 0B | 2.3MiB | 0B | | `nvim` | 1.4GiB | 0B | 578KiB | 0B | | `nvim-headless` | 389MiB | 0B | 578KiB | 0B | | `nvim-no-lsps` | 1.1GiB | 0B | 578KiB | 0B | | `nvim-no-ts` | 1.5GiB | 0B | 578KiB | 0B | | `nvim-small` | 929MiB | 0B | 578KiB | 0B |
Some checks failed
/ check (push) Successful in 8s
Required
Details
/ check-renovaterc (push) Successful in 3s
Required
Details
/ build-packages (push) Successful in 13s
Required
Details
/ build-vm (push) Failing after 26s
Required
Details
/ report-size (push) Successful in 1m2s
Required
Details
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin push-xstqnkxmwxvm:push-xstqnkxmwxvm
git checkout push-xstqnkxmwxvm
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
jalil
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jalil/configuration.nix#357
No description provided.
Delete branch "push-xstqnkxmwxvm"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?