That is by design. All import paths should be complete, absolute paths, and
that is enforced as much as possible.
When somebody moves or copy a file to another directory structure, the
program behaviour is preserved, even if by chance there is a similarly
named package nearby.
If "../serial" w
Note that if you write a project that other users would use, you will force
them to update their $GOPATH to make your app work.
Which I think it a lot worse than making people who fork your project
update the import path And like someone else said, if I need to fork a
project, I most likely alre
On Monday, February 27, 2017 at 3:18:18 PM UTC+1, Basile Starynkevitch
wrote:
>
>
>
> On Monday, February 27, 2017 at 3:02:24 PM UTC+1, C Banning wrote:
>>
>> Try organizing your project as:
>>
>> monimelt
>>
>> src
>>
>> cmd (or "monimelt", if there's just one app)
>>
>> objvalmo
>>
>> serial
> if someone wants to fork my github project, he would have change my
username bstarynk/ by his own one in every package path
When I contribute to other people's projects on Gitub, I just "go get"
their package, and adjust my "git remote" settings for the package so can
push all my changes into
On Monday, February 27, 2017 at 3:02:24 PM UTC+1, C Banning wrote:
>
> Try organizing your project as:
>
> monimelt
>
> src
>
> cmd (or "monimelt", if there's just one app)
>
> objvalmo
>
> serial
>
>
>
> Then include $HOME/monimelt in your GOPATH.
>
>>
>>
Thanks for the suggestion.
BTW, I
Try organizing your project as:
monimelt
src
cmd (or "monimelt", if there's just one app)
objvalmo
serial
Then include $HOME/monimelt in your GOPATH.
>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group a
