| 11 Jan 2024 |
 @qbit:tapenet.org | 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 |
| @qbit:tapenet.org | that can't be ref'd as "signaslbot/errUtils" | 13:33:17 |
| @qbit:tapenet.org | in go | 13:33:19 |
| @qbit:tapenet.org | because your "sub" module is literally called "errUtils" | 13:33:43 |
| @qbit:tapenet.org | remote the errUtils/go.* files and things might work | 13:34:18 |
| @qbit:tapenet.org | https://go.dev/ref/mod#modules-overview | 13:35:14 |
| @qbit:tapenet.org | your errUtils is a package in the signaslbot module | 13:35:50 |
| @qbit:tapenet.org |
Each package within a module is a collection of source files in the same directory that are compiled together. A package path is the module path joined with the subdirectory containing the package (relative to the module root). For example, the module "golang.org/x/net" contains a package in the directory "html". That package’s path is "golang.org/x/net/html".
| 13:35:51 |
| @qbit:tapenet.org | doing sub-modules is .. tricky and probably not what you want for a project of this size | 13:43:21 |
 SYMYƧ | In reply to @qbit:tapenet.org
doing sub-modules is .. tricky and probably not what you want for a project of this size Yeah I really just did that because I wanted to get more experience structuring projects this way | 16:03:46 |
| @qbit:tapenet.org | i think to do sub-modules you need to use the "full" path of the module | 16:05:34 |
| @qbit:tapenet.org | so github.com/mplsbugbounty/signaslbot | 16:06:25 |
| @qbit:tapenet.org | instead of signaslbot | 16:06:36 |
| SYMYƧ | 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 |
| SYMYƧ | In reply to @qbit:tapenet.org
so github.com/mplsbugbounty/signaslbot Okay thanks, I'll give that a shot! | 16:07:45 |
