| 2022-01-16 03:25:08 +0100 | neurocyte0917095 | (~neurocyte@IP-094046087042.dynamic.medianet-world.de) |
| 2022-01-16 03:25:08 +0100 | neurocyte0917095 | (~neurocyte@IP-094046087042.dynamic.medianet-world.de) (Changing host) |
| 2022-01-16 03:25:08 +0100 | neurocyte0917095 | (~neurocyte@user/neurocyte) |
| 2022-01-16 03:27:24 +0100 | neurocyte091709 | (~neurocyte@user/neurocyte) (Ping timeout: 250 seconds) |
| 2022-01-16 03:27:24 +0100 | neurocyte0917095 | neurocyte091709 |
| 2022-01-16 12:51:38 +0100 | <fnstudio> | hallo! thanks everyone here for kmonad, it seems a very nice tool! i wanted to point out something, if i look at https://github.com/kmonad/kmonad/blob/master/doc/installation.md#gnu-guix the $(guix build kmonad) bit doesn't (any longer?) get expanded to the intended path /gnu/store/...-kmonad-0.4.1/ |
| 2022-01-16 12:52:25 +0100 | <fnstudio> | instead, it gets expanded to /gnu/store/...-kmonad-0.4.1-static/ |
| 2022-01-16 12:54:00 +0100 | <fnstudio> | i don't think there's a straightforard way to point at the correct path just by means of a command expansion |
| 2022-01-16 12:55:02 +0100 | <fnstudio> | so i'd suggest that gets changed in the docs with a slightly less aestetically pleasant (but correct) path pattern, such as /gnu/store/...-kmonad-0.4.1/ |
| 2022-01-16 12:56:01 +0100 | <fnstudio> | what do you think? if this seems sensible, what's the best way to go about this? shall i create a tiny PR? |
| 2022-01-16 12:58:12 +0100 | <Solid> | fnstudio: the `...` part is just a hash of the binary; i.e., that would be the same for different people right? |
| 2022-01-16 12:59:33 +0100 | <fnstudio> | Solid: thanks for getting back to me; yes, the `...` would be the hash, it'd be the same for different people who are installing the software at the same point in time, but it'd change over time (i guess?) |
| 2022-01-16 12:59:45 +0100 | <fnstudio> | Solid: so, i'd recommend to have a pattern in the docs |
| 2022-01-16 13:00:06 +0100 | <fnstudio> | with the actual ellipsis `...` or something along these lines |
| 2022-01-16 13:00:40 +0100 | <Solid> | mh, is there nothing that expands to the binary that we want? manually chasing hashes doesn't sound like a very nice experience :/ |
| 2022-01-16 13:00:41 +0100 | <fnstudio> | not formally correct as in a regex, but clear for the reader, i suppose? |
| 2022-01-16 13:00:50 +0100 | <fnstudio> | Solid: true... |
| 2022-01-16 13:01:33 +0100 | <fnstudio> | Solid: i had the chance to briefly raise this in #guix before mentioning this here, and nope, unfortunately there doesn't seem to be a very direct way of doing this - unless... |
| 2022-01-16 13:01:49 +0100 | <fnstudio> | unless we're happy to add some grep or awk or similar |
| 2022-01-16 13:02:18 +0100 | <fnstudio> | which would make it for a completely automated cut-and-paste experience |
| 2022-01-16 13:02:27 +0100 | <fnstudio> | but it'd be a bit more obscure? |
| 2022-01-16 13:03:47 +0100 | <fnstudio> | ideally, there should be a more straightforward way for getting the correct path from guix, i think |
| 2022-01-16 13:04:25 +0100 | <fnstudio> | the person i spoke to on #guix suggested we could have some `guix whereis` command in the future - but that's just a possible idea for the future |
| 2022-01-16 13:08:14 +0100 | <Solid> | it would perhaps be a bit obscure, but I think it'd be worth it not having to manually find stuff |
| 2022-01-16 13:09:20 +0100 | <Solid> | fnstudio: if you want, feel free to open a PR :) |
| 2022-01-16 13:10:27 +0100 | <fnstudio> | Solid: ok, brilliant, thanks |