In my git repo (bitbucket.org) I have
reponame/
.git/
integration1/
integration2/
integration-common/
└── util
├── go.mod
└── readascii.go
The module directory is a subdirectory of the git repository. The
repository is tagged with v0.0.1.
Heres the go.mod
module
If you use `127.0.0.1:0` as your listening address then the firewall won't
trigger as well.
On Saturday, 7 November 2020 at 15:20:06 UTC+2 Aleistar Markóczy wrote:
> I may not be "using go run as a development tool" (which I would deem a
> perfectly fine reason to use "go run", I mean what
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
I may not be "using go run as a development tool" (which I would deem a
perfectly fine reason to use "go run", I mean what else would you use it
for, maybe to run on production? ;-) ) but the same happens when running go
test to run tests while creating a server to run the tests on.
The trick
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
