!9IQChSjwSHXPPWTa:lix.systems

Lix

628 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms196 Servers

Load older messages


SenderMessageTime
8 Oct 2024
@jade_:matrix.org@jade_:matrix.org
In reply to @waltmck:matrix.org
To be clear, there is no overlay which follows the nixpkgs version of Lix and I will need to hardcode until the bug filed in lix relang is done?

not only that, there cannot really exist one without it being a giant pain in the neck. maintaining date based dependencies is a pain in the neck, and it is unclear how one would even "properly" schedule one in step with nixpkgs and in step with our own release schedule since nixpkgs takes a while to get new versions of lix.

the correct way for this to be handled is if something like our overlay is upstreamed into nixpkgs itself.

01:34:16
@uep:matrix.orguep

FWIW, this is mildly annoying too.. (but not worth the effort)

❯ nix  why-depends /run/current-system /nix/store/1fp0ggfyfgn6ydsgc8sdwqv5n5gn9nal-nix-2.18.8
/nix/store/2c2dc6204dw2pqj3hrgdwdsfravvk604-nixos-system-oenone-24.11.20241004.bc947f5
└───/nix/store/iwmxfmj8iyla2lvz3a6afn898j5dgmx7-system-path
    └───/nix/store/llbdd2sm6n01m8lf6y1ix5kfzfp0d2hv-nixos-option
        └───/nix/store/1fp0ggfyfgn6ydsgc8sdwqv5n5gn9nal-nix-2.18.8
01:57:57
@uep:matrix.orguep I don't really know why the nix attribute it pulls in isn't the one overlayed to lix, but.. whatever 01:59:05
@jade_:matrix.org@jade_:matrix.org
In reply to @uep:matrix.org
I don't really know why the nix attribute it pulls in isn't the one overlayed to lix, but.. whatever
it's because of something more depressing
02:06:18
@jade_:matrix.org@jade_:matrix.orghttps://github.com/NixOS/nixpkgs/pull/31349702:06:44
@jade_:matrix.org@jade_:matrix.orgthis is the fix, it just needs flake support ripped out and the merge button pressec02:06:55
@jade_:matrix.org@jade_:matrix.org * this is the fix, it just needs flake support ripped out and the merge button pressed02:06:56
@jade_:matrix.org@jade_:matrix.orgthe thing it is replacing has no flake support and the flake support in the replacement isn't quite good enough by some peoples' estimation02:07:30
@uep:matrix.orguepsigh02:23:53
@jade_:matrix.org@jade_:matrix.orglike. they're right02:23:59
@uep:matrix.orguepI'm all for user-friendly convenience commands, but isn't this "just use the repl" ? 02:24:17
@jade_:matrix.org@jade_:matrix.org but this means that the flake support should be removed and we should ship that as a second change that is actually reviewable 02:24:20
@uep:matrix.orguepyah02:24:34
@ext0l:matrix.orgext0lfor the record i use https://github.com/NixOS/nixpkgs/issues/97855#issuecomment-1075818028 for nixos-option flake compat03:48:13
@lily:lily.flowersLily Foster
In reply to @ext0l:matrix.org
for the record i use https://github.com/NixOS/nixpkgs/issues/97855#issuecomment-1075818028 for nixos-option flake compat
i do downright criminal stuff like NIX_PATH=nixpkgs/nixos=/path/to/cursed/nixos/entrypoint/shim:nixpkgs=/path/to/normal/nixpkgs with nixos entrypoint shim https://github.com/lilyinstarlight/foosteros/blob/ae4b316dbd297d23dbd13a078b15797805109f9c/nixos.nix
04:46:39
@lily:lily.flowersLily Foster (https://github.com/lilyinstarlight/foosteros/blob/ae4b316dbd297d23dbd13a078b15797805109f9c/config/base.nix#L114 and https://github.com/lilyinstarlight/foosteros/blob/ae4b316dbd297d23dbd13a078b15797805109f9c/config/base.nix#L173 for where i'm setting NIX_PATH. but uh i'm sorry in advance to anyfew clicking those links that most of my config is overengineered, inscrutible rubbish) 04:57:00
@lily:lily.flowersLily Foster * (https://github.com/lilyinstarlight/foosteros/blob/ae4b316dbd297d23dbd13a078b15797805109f9c/config/base.nix#L114 and https://github.com/lilyinstarlight/foosteros/blob/ae4b316dbd297d23dbd13a078b15797805109f9c/config/base.nix#L173 for where i'm setting NIX_PATH. but uh i'm sorry in advance to anyfew clicking those links that most of my config is overengineered, inscrutable rubbish) 04:57:23
@ext0l:matrix.orgext0l
In reply to @lily:lily.flowers
i do downright criminal stuff like NIX_PATH=nixpkgs/nixos=/path/to/cursed/nixos/entrypoint/shim:nixpkgs=/path/to/normal/nixpkgs with nixos entrypoint shim https://github.com/lilyinstarlight/foosteros/blob/ae4b316dbd297d23dbd13a078b15797805109f9c/nixos.nix
you're right, that is criminal
05:46:46
@benjamin:computer.surgerybenjamin I think I have a misunderstanding of either what a closure is or how buildInputs works 22:18:08
@benjamin:computer.surgerybenjamin my previous understanding was that anything in buildInputs becomes part of the output path's closure, which is the thing that shows up with nix path-info --recursive (or nix copy) 22:18:28
@benjamin:computer.surgerybenjamin but I'm currently looking at the mesa package in nixpkgs, where libxshmfence is part of buildInputs, but not listed in nix path-info --recursive 22:18:58
@lily:lily.flowersLily Fosterruntime closure is done via reference scanning after building ("build closure" is distinct)22:19:19
@benjamin:computer.surgerybenjaminah that makes sense22:19:33
@benjamin:computer.surgerybenjamin so libxshmfence isn't included because none of the libraries/binaries built by the mesa package actually link it 22:20:02
@benjamin:computer.surgerybenjamin so libxshmfence isn't included because none of the libraries/binaries built by the mesa package actually link it? 22:20:10
@lily:lily.flowersLily Foster(as in it looks for any of the input store path hashes in the output store path and writes those references down and that makes up the runtime closure)22:20:15
@lily:lily.flowersLily Foster
In reply to @benjamin:computer.surgery
so libxshmfence isn't included because none of the libraries/binaries built by the mesa package actually link it?
yeah, if you were to grep for the hash part of the store path in whichever mesa output you're inspecting, it would be absent
22:20:56
@lily:lily.flowersLily Foster
In reply to @benjamin:computer.surgery
so libxshmfence isn't included because none of the libraries/binaries built by the mesa package actually link it?
* yeah, if you were to grep for the hash part of the libxshmfence store path in whichever mesa output you're inspecting, it would be absent
22:21:10
@lily:lily.flowersLily Foster(but also note that derivations can have multiple outputs, so you may only be inspecting one of the outputs and the reference could still exist in another)22:21:26
@raitobezarius:matrix.orgraitobezariusAnd as you can expect, if you apply any transformation that's not the identity to that path which is reversed at runtime, it's also absent22:21:26

Show newer messages


Back to Room ListRoom Version: 10