Hi,
I don't fully understand why we have to use replace directives (I'm
still learning my way around go modules), but I have tried extensively
to remove them and I can't get go mod to honour an acceptable set of
versions in the requirement.
I am guessing at a few potential reasons why this s
I don't quite understand why you're using replace directives here rather
than just declaring the pseudo-version as a requirement.
Why wouldn't that work?
On Fri, 6 Nov 2020, 14:19 Jim Minter, wrote:
> Hi,
>
> Using Go 1.14, I'm working on a parent codebase which, in its go.mod
> file, has a num
Hi,
Using Go 1.14, I'm working on a parent codebase which, in its go.mod
file, has a number of replace statements referencing legacy child
codebases which have not yet converted to Go modules.
At this stage the legacy child codebases handle versioning by branch,
rather than using semantic ve
