2 ms·
It's important to note that it still doesn't apply to downstream users (those adding your package to their go.mod), only to those building your package directly
by tsimionescu 5y ago
It's important to note that it still doesn't apply to downstream users (those adding your package to their go.mod), only to those building your package directly. I think this decision makes sense, so this is not a complaint.
- caust1c 5y agoCan you elaborate? We use `replace` everywhere in our codebase for modules that we've forked + modified.
- tsimionescu 5y agoAssume module A depends on module B, and module B has a dependency on module github.com/C, and a replace rule for github.com/C => company.internal/C. When you build module A, it will pull module B and module github.com/C, instead of B and company.internal/C, unless A has its own replace directive for C.