jalil/blog
1
0
Fork 0
Code Issues 1 Pull requests Activity Actions

Update flake and configure CI #1

Merged
jalil merged 2 commits from push-rkpumpksllmt into main 2025-10-05 15:58:41 +02:00
Conversation 1 Commits 2 Files changed 5 +109 -12
jalil commented 2025-10-05 15:54:28 +02:00
Owner
Copy link

I'll just mirror this over to GH but do development here.

I'll just mirror this over to GH but do development here.
jalil self-assigned this 2025-10-05 15:54:28 +02:00 
Signed-off-by: Jalil David Salamé Messina <jalil.salame@gmail.com>
ci: configure forgejo CI
All checks were successful
/ check-renovaterc (push) Successful in 12s
Details
/ checks (x86_64-linux, treefmt) (pull_request) Successful in 13s
Details
/ build (pull_request) Successful in 4s
Details
/ report-size (pull_request) Successful in 20s
Details
80f66b0f36
 
Nice to have

Signed-off-by: Jalil David Salamé Messina <jalil.salame@gmail.com>
forgejo-actions commented 2025-10-05 15:55:08 +02: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/Home-Manager 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.

Packages

Name Size Size Change NAR Size NAR Size Change
default 2.0MiB 2.0MiB 2.0MiB 2.0MiB
site 2.0MiB 120B 2.0MiB 120B
<!-- 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/Home-Manager 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> ## Packages | Name | Size | Size Change | NAR Size | NAR Size Change | |------|-----:|------------:|---------:|----------------:| | `default` | 2.0MiB | 2.0MiB | 2.0MiB | 2.0MiB | | `site` | 2.0MiB | 120B | 2.0MiB | 120B |
jalil force-pushed push-rkpumpksllmt from 80f66b0f36 to 45a94657cd 2025-10-05 15:58:21 +02:00 Compare
jalil merged commit 45a94657cd into main 2025-10-05 15:58:41 +02:00
jalil deleted branch push-rkpumpksllmt 2025-10-05 15:58:41 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working

  
chore

Small fix/cleanup

  
enhancement

New feature

No labels
bug
chore
enhancement
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/blog#1
No description provided.
Delete branch "push-rkpumpksllmt"

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?