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

feat: switch to fish as an interactive shell #375

Merged
jalil merged 1 commit from push-wzkrsvyqulvy into main 2025-03-24 21:23:49 +01:00
Conversation 3 Commits 1 Files changed 6 +117 -139
jalil commented 2025-03-23 21:57:01 +01:00
Owner
Copy link

Now that it is written in Rust I am interested!

Now that it is written in Rust I am interested!
jalil self-assigned this 2025-03-23 21:57:01 +01:00
jalil added 1 commit 2025-03-23 21:57:02 +01:00
feat: switch to fish as an interactive shell
All checks were successful
/ check (push) Successful in 36s
Details
/ check-renovaterc (push) Successful in 2s
Details
/ build-packages (push) Successful in 37s
Details
/ build-vm (push) Successful in 1m5s
Details
/ report-size (push) Successful in 1m13s
Details
615cf82b52 
Now that it is written in Rust I am interested!
forgejo-actions commented 2025-03-23 22:00:30 +01:00
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.1GiB 132MiB 19KiB 0B

Packages

Name Size Size Change NAR Size NAR Size Change
audiomenu 42MiB 0B 1.4MiB 0B
docs 3.1MiB 0B 3.1MiB 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.6GiB 203MiB 578KiB 0B
nvim-headless 441MiB 49MiB 578KiB 0B
nvim-no-lsps 1.2GiB 49MiB 578KiB 0B
nvim-no-ts 1.7GiB 203MiB 578KiB 0B
nvim-small 997MiB 49MiB 578KiB 0B
search 728KiB 0B 9.0KiB 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.1GiB | 132MiB | 19KiB | 0B | ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `audiomenu` | 42MiB | 0B | 1.4MiB | 0B | | `docs` | 3.1MiB | 0B | 3.1MiB | 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.6GiB | 203MiB | 578KiB | 0B | | `nvim-headless` | 441MiB | 49MiB | 578KiB | 0B | | `nvim-no-lsps` | 1.2GiB | 49MiB | 578KiB | 0B | | `nvim-no-ts` | 1.7GiB | 203MiB | 578KiB | 0B | | `nvim-small` | 997MiB | 49MiB | 578KiB | 0B | | `search` | 728KiB | 0B | 9.0KiB | 0B |
jalil commented 2025-03-23 22:04:06 +01:00
Author
Owner
Copy link

I need to test it in the VM to see how it looks, but I'm hopeful c:

I need to test it in the VM to see how it looks, but I'm hopeful c:
jalil force-pushed push-wzkrsvyqulvy from 615cf82b52 to cd4fb19335 2025-03-24 21:20:12 +01:00 Compare
jalil commented 2025-03-24 21:22:56 +01:00
Author
Owner
Copy link

@jalil wrote in #375 (comment):

I need to test it in the VM to see how it looks, but I'm hopeful c:

Fixed some bugs and now it looks good!

@jalil wrote in https://git.salame.cl/jalil/configuration.nix/pulls/375#issuecomment-4697: > I need to test it in the VM to see how it looks, but I'm hopeful c: Fixed some bugs and now it looks good!
jalil scheduled this pull request to auto merge when all checks succeed 2025-03-24 21:23:00 +01:00
jalil merged commit cd4fb19335 into main 2025-03-24 21:23:49 +01:00
jalil deleted branch push-wzkrsvyqulvy 2025-03-24 21:23:49 +01:00
jalil referenced this pull request from a commit 2025-03-24 21:26:36 +01:00
chore(flake): update inputs
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
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#375
No description provided.
Delete branch "push-wzkrsvyqulvy"

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?