| 7 Jun 2024 |
 puck | i mean, if you want to, you can just add __json as an attribute to a drv and do the same | 21:52:41 |
 jade_ | is that how we store those? holy fucik | 21:52:58 |
| jade_ | * is that how we store those? holy fuck | 21:53:02 |
| jade_ | just shove some json string in there? ??? | 21:53:13 |
| puck | yup. structuredAttrs is stored by just creating a big ass-__json environment variable | 21:53:15 |
| jade_ | we should not expose such internals O_o | 21:53:21 |
| jade_ | you should not be allowed to dump __json in from nixlang | 21:53:46 |
| puck | nix-repl> runCommandNoCC "meow" { __structuredAttrs = true; } "meow"
«derivation /nix/store/3isnlphfrgws22950l9i2hciq1a2j8vb-meow.drv»
puckipedia@marisa ~> nix --extra-experimental-features nix-command derivation show /nix/store/3isnlphfrgws22950l9i2hciq1a2j8vb-meow.drv | jq '."/nix/store/3isnlphfrgws22950l9i2hciq1a2j8vb-meow.drv".env.__json'
"{\"buildCommand\":\"meow\",\"buildInputs\":[],\"builder\":\"/nix/store/h3bhzvz9ipglcybbcvkxvm4vg9lwvqg4-bash-5.2p26/bin/bash\",\"cmakeFlags\":[],[..],\"propagatedBuildInputs\":[],\"propagatedNativeBuildInputs\":[],\"stdenv\":\"/nix/store/lgam1kdqv5fbkwwcs7msjj9a2a5s5i4h-stdenv-linux\",\"strictDeps\":false,\"system\":\"x86_64-linux\"}"
| 21:54:23 |
| puck | In reply to @jade_:matrix.org
you should not be allowed to dump __json in from nixlang consider, though: you can create a .drv that compiles differently in post-structuredAttrs and pre-structuredAttrs nix | 21:56:41 |
| puck | what do you mean "noone runs pre-2.0 nix" | 21:57:18 |
| puck | * what do you mean "noone runs pre-2.0 nix" | 21:57:20 |
 Lily Foster | In reply to @puck:puck.moe
yup. structuredAttrs is stored by just creating a big ass-__json environment variable (i see what you did with the hyphen there) | 22:23:11 |
| Lily Foster | (https://xkcd.com/37/) | 22:23:59 |
 Qyriad | Oh wow that's an old one | 23:06:25 |
| 8 Jun 2024 |
| jade_ | haunted | 06:42:22 |
| jade_ | 
Download image.png | 06:42:24 |
| jade_ | i believe that should be "impossible" | 06:42:35 |
| jade_ | why do we realise an output that already exists and not fail some kind of check? | 06:42:45 |
| jade_ | oh wait | 06:43:41 |
| jade_ | nvm | 06:43:43 |
| jade_ | 
Download image.png | 07:08:59 |
| jade_ | ok this is pretty satisfying ^_^ | 07:09:08 |
| jade_ | container image: not only way less busted in re layering, also way smaller | 07:09:27 |
 delroth | is there already a hydra fork somewhere which builds with Lix? (or does it build without changes? I doubt so) | 13:46:59 |
| delroth | didn't find one in the lix-project forgejo org | 13:47:13 |
|  AkechiShiro joined the room. | 14:17:12 |
| delroth | https://gerrit.lix.systems/c/lix/+/1418 I got annoyed at not being able to just use Lix as a flake with a recent nixpkgs version, please flame me if you think this shouldn't be done before Lix 2.90 is tagged :p | 15:02:04 |
 aprl | In reply to @delroth:delroth.net
is there already a hydra fork somewhere which builds with Lix? (or does it build without changes? I doubt so) hot take: dropping Hydra and rebuilding a new Lix based CI from scratch | 15:04:47 |
 K900 | Can you get that done by next week? :) | 15:05:18 |
| aprl | In reply to @k900:0upti.me
Can you get that done by next week? :) by next week, within one week, whats the challenge here exactly? | 15:05:47 |
