!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

222 Members
https://github.com/nixpkgs-architecture, weekly public meetings on Wednesday 15:00-16:00 UTC at https://meet.jit.si/nixpkgs-architecture50 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
10 Jan 2025
@connorbaker:matrix.orgconnor (burnt/out) (UTC-8) joined the room.04:41:29
@xanderio:bitflip.jetztxanderio joined the room.09:16:16
@kjeremy:matrix.orgkjeremy joined the room.13:30:18
11 Jan 2025
@lucasew:matrix.orgLucas Eduardo
In reply to @hsngrmpf:matrix.org

Hey Folks, I have a question regarding splicing.

I am recently hunting cross related issues and I'm trying to wrap my head around why it works how it works.

My question is: Why do we add __spliced to packages by traversing the top-level?
eg, why is splicing not done in mkDerivation? Why is not every package spliced by default? Wouldn't that be simpler?

The problems I currently see:

  • Everything that is not in the top level package set is not spliced.
  • dynamic interactions like overrides seem to break splicing (no __spliced after overriding).

It seems to me that this would not be an issue if mkDerivation itself would take care of the splicing. But probably I'm missing something and I would like to understand what.

John Ericson infinisil Robert Hensing (roberth)

What is the deal with splicing? What is it? Is there any doc around the concept?
22:44:45
@philiptaron:matrix.orgPhilip Taron (UTC-8)It's not a doc, but I found this whole thread worth reading. https://discourse.nixos.org/t/frustrations-about-splicing/4960723:00:25
12 Jan 2025
@strutztm:strutztm.de@strutztm:strutztm.de joined the room.00:25:08

Show newer messages


Back to Room ListRoom Version: 9