Lix | 1114 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-rooms | 300 Servers |
| Sender | Message | Time |
|---|---|---|
| 16 May 2024 | ||
Also I deliberately pulled in this wrong version when doing a nix flake update on a path dependency. I feel like Lix didn't really have a chance to give me any useful hints to stop me. (Except for maybe showing me the branch name (and repo status) if the path depency is a VCS repo, I guess?) | 18:47:21 | |
| Yeah, alas | 18:51:58 | |
| vringar: if you don't like waiting for builds, you would like to do a wrapper thingy. there's a very funny hack you can do with a thing called https://github.com/lf-/dotfiles/blob/9efe16ccf1ab93f2464cf4e4fe871e67d5b89f06/configs/nix/roles/kanidm/default.nix#L25-L32 | 19:07:38 | |
| raito taught me that one. there's so many wicked little tricks around. | 19:08:42 | |
In reply to @jade_:matrix.orgThat feels like it should be in lib? | 19:09:04 | |
| Or is it too cursed? | 19:09:11 | |
In reply to @ff-vringar:mozilla.orgit can't be, since it's a derivation | 19:09:21 | |
| it would be a trivial builder if anything | 19:09:26 | |
In reply to @jade_:matrix.orgRight. Builders aren't in lib. They are useful functions that exist in pkgs. Need to internalize that still | 19:10:47 | |
In reply to@jade_:matrix.orgIt is: pkgs.symlinkJoin | 19:10:54 | |
In reply to@ff-vringar:mozilla.orgYeah pkgs has no separation between useful functions and builders and fetchers, and actual packages | 19:11:31 | |
In reply to @qyriad:katesiria.orgthat's a different thing iirc | 19:12:02 | |
| oh maybe | 19:12:38 | |
In reply to @qyriad:katesiria.orgRFC for pkgs.lib xD | 19:13:19 | |
That's just lib | 19:13:59 | |
lib is literally pkgs.lib, and not only that, there used to be pkgs-lib, which they removed (though that was before our time so we don't know the motivations for why) | 19:14:27 | |
In reply to @qyriad:katesiria.orgoh lol. I realize I should make go poke through nixpkgs before trying to make jokes. | 19:15:29 | |
In reply to @jade_:matrix.orgyeahh... there's so much of general-purpose utilities that should live higher up randomly living in some dark corner of nixpkgs because someone happened to need it there heh | 19:22:48 | |
| which I mean, I kinda do get | 19:22:55 | |
| (also that's a neat one, didn't know about that :o) | 19:23:20 | |
| oh though I suppose that one is actually from X, but ye weird place for it :p | 19:25:04 | |
| i mean, it is from xorg, it's not strangely placed, it's just strange that there aren't other tools to do the same thing | 19:30:58 | |
| | 19:33:55 | |
| jade_: yeah I realised afterward, but I mean like, strange place for such a tool to live in the first place (as in, in upstream xorg) | 19:38:59 | |
Back to the next question (now with proper branches): I've updated my package.nix to better show the problem.Even though I build ghidraWithName.withExtensions the makeBinaryWrapper still picks up the unmodified ghidra and I can't find the correct syntax for an override to set ghidra: ghidraWithNameThis issue can be verified by running nix develop and then less $(which ghidra) and inspecting the embedded text.However, directly building the package with nix build puts the correct package into result (verifiable with tail result/lib/ghidra/support/launch.properties) | 19:43:23 | |
| * Back to the next question (now with proper branches): I've updated my Where do I need to set the override? | 19:44:01 | |
| * Back to the next question (now with proper branches): I've updated my Where and how do I need to override? | 19:44:36 | |
In reply to @ff-vringar:mozilla.orgyou are naming different things in devShells.default and packages.default | 19:45:53 | |
Yes, because packages.default works (has the modified launch.properties) but the devShell (which links in the extensions) references the unmodified package (through the binary wrapper) | 19:47:31 | |
* Yes, because packages.default works (has the modified launch.properties) but the devShell (which links in the extensions) references the unmodified package (through the binary wrapper) | 19:48:10 | |