| 14 Aug 2025 |
 Artem | there must be examples somewhere but I'm not very good at finding the minimal one. I see overrideSrc and overrideCabal but both look a bitt low level | 15:10:01 |
| Artem | I'm guessing the versions are specified in configuration-hackage2nix/main.yml | 15:23:38 |
| Artem | it says "# This is a list of packages with versions from the latest Stackage LTS release." sadly, it doesn't explicitly say if I can add packages outside of LTS in there | 15:24:56 |
| Artem | but the name of its "extra-packages" field suggested that it's the right place | 15:25:47 |
 maralorn | There is stackage.yaml file, which is auto generated. | 15:25:57 |
| Artem | I don't need that one for adding a non-stackage package, right? | 15:26:50 |
| maralorn | Yeah. | 15:27:18 |
| maralorn | Then there is extra-packages which gives additional versioned attributes. | 15:28:14 |
| Artem | my slight worry about configuration-hackage2nix/main.yml#extra-packages is that every package on that list has a comment saying why it's there, and it's very specific. This makes me question that it's the right place. Unless I'm expected to say "# it's a cool package not on Stakage, but I want it in nixpkgs"... | 15:28:24 |
| maralorn | And default-package-overrides which modifies which version the default attribute has. | 15:29:17 |
| Artem | but adding a package not from Stackage is shouldn't overide anything, so this field isn't applicable, right? | 15:31:41 |
| Artem | * but adding a package not from Stackage shouldn't overide anything, so this field isn't applicable, right? | 15:31:48 |
| Artem | * but adding a package not from Stackage shouldn't override anything, so this field isn't applicable, right? | 15:31:52 |
