Hi all,

First off, I've read this, and the other FAQ answers:
https://github.com/golang/go/wiki/Modules#is-it-possible-to-add-a-module-to-a-multi-module-repository

However, I'm not sure how my case fits the scenarios described therein; or 
maybe I just don't understand how it is related.

Previously, we had only one module: github.com/autograde/aguis

But I discovered to my dismay, that my course's tests, which depended on 
the github.com/autograde/aguis module only to get the kit package, were 
pulling in all of aguis's dependencies, instead of just the kit package. 
Previously, I kept the kit package in a separate repo (as is recommended in 
the FAQ), but this was also problematic, as it is easy to forget to update 
both for changes to one that impacts the other. Hence, I decided it would 
be best to create a separate module for the kit package: 
github.com/autograde/aguis/kit

The aguis module depends on the kit module, but not the other way around. 
However, other repos (like my course's tests) do depend on the kit module. 

Currently there are no releases for neither module; So far this has been 
working fine, until I created the new kit module. It worked for a while, 
but as we made further commits to the aguis module, we started seeing the 
messages below when the tests were trying to fetch the kit module:

github.com/autograde/aguis/kit@v0.0.0-20200326190951-c1090b5a8d9a: invalid 
version: unknown revision c1090b5a8d9a

I've read about similar problems on the issue tracker, but wasn't able to 
find a solution from those.

Anyone here have any recommendations on what is the best approach to solve 
this?

PS: I'm also using GOPROXY=direct

Thanks,
:) Hein

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/fa8832c1-bbe1-4146-8207-ade82e84dca2%40googlegroups.com.

Reply via email to