!9IQChSjwSHXPPWTa:lix.systems

Lix

1126 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-rooms312 Servers

Load older messages


SenderMessageTime
31 Mar 2026
@raitobezarius:matrix.orgraitobezariusare you on NixOS?13:56:52
@raitobezarius:matrix.orgraitobezariuson non-NixOS, it seems like you could just install Lix using its installer13:56:59
@raitobezarius:matrix.orgraitobezariuson NixOS, you can simply rebuild your NixOS config?13:57:07
@neobrain:matrix.orgneobrainperhaps you already know, but worth mentioning that a custom store location comes with baggage; most notably you'll be unable to use binary caches (... unless you generate them yourself from your custom prefix)14:13:08
@neobrain:matrix.orgneobrain(not sure to what extent it's supported in the first place. I remember a recent-ish talk about it at one of the nix conferences)14:13:44
@lisanna-dettwyler:matrix.orgLisanna you can use a store in a different location and have caching work fine, it's the store prefix (store-dir) that breaks caching if you change it 16:00:42
@lisanna-dettwyler:matrix.orgLisanna * you can use a store in a different location and have caching work fine, it's the store prefix (nix/store) that breaks caching if you change it 16:02:20
@lisanna-dettwyler:matrix.orgLisanna it's a little confusing, but a local --store can be wherever you want on your filesystem and caching will work fine, the ?store= should generally never change from /nix/store (it'll just fully resolve to e.g. /tmp/mystore/nix/store instead) 16:04:24
@neobrain:matrix.orgneobrainohh interesting16:13:55
@neobrain:matrix.orgneobrainbut I always thought that the absolute store path would be hardcoded e.g. into the DT_NEEDED entries of ELF files - how can that work if the store path is in a different location?16:15:10
@neobrain:matrix.orgneobrain * but I always thought that the absolute store path would be hardcoded e.g. into the DT_NEEDED entries of ELF files - how can that work if the store is in a different location? 16:15:15
@neobrain:matrix.orgneobrain* but I always thought that the absolute store path would be hardcoded e.g. into the RUNPATH entries of ELF files - how can that work if the store is in a different location?16:16:13
@aloisw:kde.orgaloisw There are two ways to have a store in a different location: chroot store (enabled by store setting) which can reuse the cache but needs chroot (or similar) to actually run stuff, and changing the store directory (NIX_STORE_DIR environment variable) which does not need chroot but rebuilds everything (and breaks things that hardcode /nix/store). 16:23:25
@neobrain:matrix.orgneobrainah, that makes sense16:28:06
@charles:computer.surgeryCharles terminology question: is (_: {}) the fixpoint or is lib.fix (_: {}) the fixpoint 17:20:03
@charles:computer.surgeryCharles * terminology question: is _: {} the fixpoint or is lib.fix (_: {}) the fixpoint 17:20:30
@charles:computer.surgeryCharles or maybe, is _ the fixpoint 17:26:54
@charles:computer.surgeryCharleshttps://nixos.org/manual/nixpkgs/stable/#auto-generated-11-1.6.317:28:23
@charles:computer.surgeryCharles sounds like lib.fix (_: {}) is the fixed point 17:28:31
@charles:computer.surgeryCharles * sounds like lib.fix (_: {}) is the fixpint 17:28:34
@charles:computer.surgeryCharles * sounds like lib.fix (_: {}) is the fixpoint 17:28:36
@charles:computer.surgeryCharles

in the example in that section it has:

# Calculate the fixed point of all composed overlays.
fixedpoint = lib.fix (lib.extends extensions original );
17:29:33
@aloisw:kde.orgaloisw Both lib.fix (_: {}) and _ should be the fixpoint if I'm not confusing things. 17:30:38
@charles:computer.surgeryCharlesgood point17:31:16

There are no newer messages yet.


Back to Room ListRoom Version: 10