Nix + Go | 239 Members | |
| Go packaging for and with Nixpkgs. | Be excellent to each other. | 49 Servers |
| Sender | Message | Time |
|---|---|---|
| 10 Jan 2024 | ||
In reply to @qbit:tapenet.orgthanks, I'll give it a shot once I get a chance | 01:46:28 | |
In reply to @qbit:tapenet.org Like from here:
| 01:47:34 | |
| And
| 01:48:16 | |
| It's a function argument right? | 01:48:38 | |
| oh, lib is the "nixpkgs" library | 02:12:15 | |
| https://teu5us.github.io/nix-lib.html | 02:12:36 | |
the "with lib" is effectively exposing the stuff in lib to the attrs that follow - so you don't have to type lib.maintainers.foxpy or lib.licenses.... | 02:13:53 | |
| Ohhhhh okay thank you!! | 02:15:37 | |
| np | 02:16:25 | |
| 11 Jan 2024 | ||
| Okay so I updated my
I get:
| 05:42:06 | |
| signaslbot/errUtils is a custom package in the same repo | 05:43:08 | |
| * signaslbot/errUtils is a custom package in the same repo. How can I make it available to the nix store before it gets to this build step? | 05:45:16 | |
| if you want it to be a shell you need to use mkShell, no? | 13:31:30 | |
| https://github.com/mplsbugbounty/signASLBot/blob/main/go.mod#L1 ah, i see you have a second go.mod in the errUtils dir | 13:32:54 | |
| that can't be ref'd as "signaslbot/errUtils" | 13:33:17 | |
| in go | 13:33:19 | |
| because your "sub" module is literally called "errUtils" | 13:33:43 | |
| remote the errUtils/go.* files and things might work | 13:34:18 | |
| https://go.dev/ref/mod#modules-overview | 13:35:14 | |
| your errUtils is a package in the signaslbot module | 13:35:50 | |
| 13:35:51 | |
| doing sub-modules is .. tricky and probably not what you want for a project of this size | 13:43:21 | |
In reply to @qbit:tapenet.orgYeah I really just did that because I wanted to get more experience structuring projects this way | 16:03:46 | |
| i think to do sub-modules you need to use the "full" path of the module | 16:05:34 | |
so github.com/mplsbugbounty/signaslbot | 16:06:25 | |
instead of signaslbot | 16:06:36 | |
| I've been thinking a lot lately that a good way to structure programs is to write a library and then implement the app using that library. And errUtils contains some code that I've just been copying around between my go programs so it seemed a good first candidate. | 16:07:23 | |
In reply to @qbit:tapenet.orgOkay thanks, I'll give that a shot! | 16:07:45 | |
In reply to @qbit:tapenet.orgI'm having some issues still after trying renaming the submodule paths in a few different ways. When you say remote the errUtils.go.* files, you mean like just make a new repo for them? I guess that would make more sense anyway. | 19:30:23 | |
| no, I was suggesting making them just a package, not a full blown submodule | 19:31:03 | |