go mod and replace directive does not work well when consumed as library

[ramonskie]

when we consume om in our own go library above version 0.51.0
go mod will fail. because it won't inherent the replace directive.
which then result in a compile error due to a missing dependency
see line: https://github.com/pivotal-cf/om/blob/master/go.mod#L44

i think this can be solved by
removing the replace directive and use the folowing instead
go mod edit https://github.com/graymeta/stow@TheCommitHasYouWantToUse

refrence: golang/go#30354

[jtarchie]

I don't believe that would help at all. As upstream dependency's go.mod files don't appear to be honored at all.

So if you go get github.com/pivotal-cf/om, even though it has a go.mod file, the go get does nothing with it with you go.mod file.

[jtarchie]

Why are you inheriting om as a dependency, too? At the moment we make no library guarantees about the source code. Just the CLI.

[ramonskie]

we are building an easy way to configure opsman+tiles
https://github.com/starkandwayne/om-configurator

[kcboyle]

It would really help us, you, (and other om consumers out!) if y'all could bug the stow team by giving a shout out to this issue (WasabiAiR/stow#197). If we can get the associated PR accepted, this should solve your problem. As we don't seem to be able to get around the go.mod bug (that they don't see as a bug), this seems like a good solution) @ramonskie

[ramonskie]

they have merged it.
can you update you go.mod as well?

[kcboyle]

we can. We are in the middle of fixing the CI at the moment, so feel free to submit a PR, or we should be able to get to it either today, tomorrow, or, at worst, sometime early next week.

[ramonskie]

fixed in be5a7f8#diff-37aff102a57d3d7b797f152915a6dc16