| 16 May 2024 |
 Qyriad | In reply to@jade_:matrix.org
Qyriad: ok if we stage the libnixexpr->liblixexpr etc change? Yes, absolutely. If you are getting to it before us feel free! | 22:58:53 |
 jade_ | alrighty | 22:58:58 |
| Qyriad | In reply to@delroth:delroth.net
nah I think that if you had explained your envisioned fix it would have been fairly trivial but having to independently come to the same conclusion without having the same background was harder :P Yes we absolutely should have done that. I think in retrospect we may also have been somewhat confused, since the crash doesn't happen on Nix 2.3 because of course Nix 2.3 didn't have the ^ feature | 22:59:37 |
 delroth | also re: docs thanks for the pointer, I checked many manual pages (incl. "nix build"), I checked the glossary, etc. and of course didn't think of checking the generic "nix CLI" page | 22:59:55 |
| delroth | doesn't even really make sense that it's there because I think it's only a "build" feature anyway? | 23:00:06 |
| delroth | ah no, there's examples there with path-info | 23:00:19 |
| Qyriad | Yeah, the nix build and co pages now at least have a link to the generic "nix CLI page" saying that that's where installables are documented, but it needs to be so much more | 23:00:28 |
| Qyriad | and actually things like nix shell and nix develop can also use this syntax | 23:00:55 |
| Qyriad | Basically any nix3 command that might also realise in the process can do that | 23:01:11 |
| delroth | what does it mean to nix develop an output | 23:03:09 |
| Qyriad | fantastic question. | 23:03:51 |
| delroth | yeah. | 23:03:58 |
 puck | it uhhhhhhhhh | 23:04:00 |
| puck | sources $stdenv/setup, then does some churning to output the list of all variables and functions | 23:04:40 |
| puck | why is this part of Nix. this is nixpkgs-specific | 23:04:51 |
| delroth | yeah but all that is derivation specific, nothing that has to do with outputs | 23:05:27 |
| puck | oh! so | 23:06:04 |
| delroth | I'd guess it's just being ignored? | 23:06:17 |
| puck | you can nix develop a path that ends with -env and it'll .. just return an existing env file | 23:06:21 |
| Qyriad | just ran a nix develop on openssl^bin and openssl^lib and envd in both of them and there was zero difference | 23:06:22 |
| Qyriad | wait what | 23:06:45 |
| puck | okay, sec, this is a bit tricky to show | 23:06:57 |
| puck | okay so i just ran nix develop -vvvv, and grabbed the building of '/nix/store/ivs7b52v8h757wr2m7c00z5y958w33k1-nix-shell-env.drv^*' from .drv file: created line | 23:07:49 |
| delroth | also | 23:07:50 |
| Qyriad | In reply to@puck:puck.moe
why is this part of Nix. this is nixpkgs-specific the general problem of nix being so poorly interoperable that it has to do everything itself >.> | 23:07:55 |
| delroth | $ nix develop /nix/store/dr53sp25hyfsnzjpm8mh3r3y36vrw3ng-neovim-0.9.5^out
nix: src/libstore/derivations.cc:931: static std::string_view nix::BasicDerivation::nameFromPath(const nix::StorePath&): Assertion `nameWithSuffix.ends_with(extension)' failed.
| 23:07:59 |
| delroth | so yeah | 23:08:02 |
| delroth | let's fix the parser | 23:08:04 |
| Qyriad | yeah | 23:08:17 |
| puck | building that got me /nix/store/jnwd23hwyh8vim1k0pbnjp6843sl2xl9-nix-shell-env and i can just like. nix develop that store path, it looks like | 23:08:32 |
