Re: [go-nuts] Re: Forking/transfering a repository and import paths

2018-12-12 Thread robert engels
It was called “sneaker-net” in my day… what a PITA > On Dec 12, 2018, at 4:24 PM, Sotirios Mantziaris > wrote: > > would this one the problem of forking or transfer to another account? The go > module path would still be the old one. > Like mentioned before it would be nice if the hosting path

Re: [go-nuts] Re: Forking/transfering a repository and import paths

2018-12-12 Thread Sotirios Mantziaris
would this one the problem of forking or transfer to another account? The go module path would still be the old one. Like mentioned before it would be nice if the hosting path and the module path could be different e.g. hosting path github.com/mantzas/test module path "test". On Thu, Dec 13, 2018

Re: [go-nuts] Re: Forking/transfering a repository and import paths

2018-12-12 Thread Tamás Gulácsi
With go modules you can import whatever/btcutil and force to be ../btcutil (see the replace directive). -- 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, send an email to golang-nu

Re: [go-nuts] Re: Forking/transfering a repository and import paths

2018-12-12 Thread Dave MacFarlane
Relative import paths was a feature in old versions of Go and explicitly removed *because* of Go modules: https://github.com/golang/go/issues/26645 https://github.com/golang/go/issues/27224 On Wed, Dec 12, 2018 at 1:52 PM Sotirios Mantziaris wrote: > > I was under the impression that go modules

Re: [go-nuts] Re: Forking/transfering a repository and import paths

2018-12-12 Thread Robert Engels
I’ll admit I thought that modules would solve this problem as well, which is why I stopped worrying about it, but in the module examples I’ve reviewed I don’t see it addressing this, but I’m probably wrong. I think a clear example of how this is addressed with modules would be very beneficial.

[go-nuts] Re: Forking/transfering a repository and import paths

2018-12-12 Thread Sotirios Mantziaris
I was under the impression that go modules would do that kind of separation. When creating a module you define the module path. If the project is hosted in github, bitbucket or anywhere else should not matter. when calling go get github.com/user/application you refer just to the path where the re

[go-nuts] Re: Forking/transfering a repository and import paths

2018-12-12 Thread Louki Sumirniy
I have done this many times. Some repositories are more of a pain than others to move. I was amused to learn after having done this with github.com/btcsuite/btcd, that the btcjson, btcec, btcutil and btclog repos all were separate but quite tightly bound both to each other and it took me about