Thanks a bunch.

Based on these, I should be including the repo name in my imports - even 
for private packages. If the repo changes, then the code has to be edited. 
For example I use an in-house instance of say bitbucket and then publish to 
the world on GitHub ,the sources will have to change to point to the new 
repo (for the internal packages)

Am I reading these wrong?

srini


On Tuesday, January 28, 2020 at 2:36:14 AM UTC-5, Lutz Horn wrote:
>
> Take a look at these blog articles: 
>
> https://blog.golang.org/using-go-modules 
> https://blog.golang.org/migrating-to-go-modules 
>
> Lutz 
>
> ________________________________________ 
> Von: golan...@googlegroups.com <javascript:> <golan...@googlegroups.com 
> <javascript:>> im Auftrag von R Srinivasan <s...@srin.me <javascript:>> 
> Gesendet: Dienstag, 28. Januar 2020 00:29 
> An: golang-nuts 
> Betreff: [go-nuts] go modules and internal packages 
>
> I have so far not migrated towards the new go modules. I am beginning the 
> process. Looking for ideas. 
>
> I split my applications into indepe 
>
> -- 
> 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 golan...@googlegroups.com <javascript:><mailto:
> golang-nuts+unsubscr...@googlegroups.com <javascript:>>. 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/golang-nuts/fea9c93a-bb07-4f90-adcf-ebc5f6c71ae5%40googlegroups.com
> <
> https://groups.google.com/d/msgid/golang-nuts/fea9c93a-bb07-4f90-adcf-ebc5f6c71ae5%40googlegroups.com?utm_medium=email&utm_source=footer>.
>  
>
>

-- 
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-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/30e1ee3e-df14-4ca0-8ec6-24e7ef597fdb%40googlegroups.com.

Reply via email to