Sorry I forgot 1 more expectation/boundary condition: I'd like to be
able to tar both go code in the local filesystem and the referenced go
packages in the local filesystem and copy it to a different OS to
different absolute paths?
I believe I can't use replace?
On 3/24/21, fge...@gmail.com wrot
> I believe I can't use replace?
I'm glad the vendoring solution is what you want. But IIUC what you are
trying to do, then there is no reason you can not use replace. For example:
require gergrly/otherpackage v0.0.0
replace gergrly/otherpackage => ../otherpackage
This works for me. You could
You can just tar up your ~/go/pkg/mod directory (plus your own sources) and
you will be good.
On Wednesday, 24 March 2021 at 16:19:13 UTC jake...@gmail.com wrote:
> > I believe I can't use replace?
>
> I'm glad the vendoring solution is what you want. But IIUC what you are
> trying to do, then
You can use the vendor folder, just copy (or symlink, but you will need to
keep them updated) what you need there and will work.
--
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, sen
Thanks, that's exactly what I was looking for!
For the next go programmer looking for a solution in similar situation:
on page https://golang.org/ref/mod#vendoring
"... or to ensure that all files used for a build are stored in a
single file tree"
On 3/24/21, Miguel Angel Rivera Notararigo wro
Thanks to both you and jake!
I remembered something similar to "import path should not be relative
paths". (Otoh the replace directive is not an import path, so I should
have checked before asking this.)
Anyways, thanks again!
On 3/24/21, Amnon wrote:
> You can just tar up your ~/go/pkg/mod dir
