On Mon, Nov 20, 2017 at 5:03 AM, Ally Dale wrote:
>
> 4. "#/xxx" style reference seems a best solution like "vendor" to fix
> local-package reference problem.
>
Without any hard code "where I am" exists in any go files.
>
And it will works well together with current global-style, because "#" will
Thanks for replying all above.
The main point of this topic is probably to discuss "what's the right way
to manage local-only packages".
1. Axel has point out that "why local-packages is not necessary in golang"
2. Jake has given an effective way to use "vendor" path to fix
local-refering problem
On Sat, Nov 18, 2017 at 12:19 PM, Ally Dale wrote:
> Hi,
>
> Here are two examples of "hello world" main packages:
> /withoutlocal
> /withlocal <- github.com/vipally/localpackage/local
>
> "withoutlocal" works well anywhere is, even out of GoPath.
> "withlocal" works only when " =
> /github.com
Hi,
Here are two examples of "hello world" main packages:
/withoutlocal
/withlocal <- github.com/vipally/localpackage/local
"withoutlocal" works well anywhere is, even out of GoPath.
"withlocal" works only when " =
/github.com/vipally/localpackage"
How does go team think about this difference?
What kind of confuses me around these discussions is, that there are rarely
complains about having to do the same thing with, say, python libraries. If
I press "fork" on a python library on github, people can't just "pip
install" it and get crackin'. They have to manually clone it and put it in
the
On Friday, 17 November 2017 02:43:48 UTC+1, Ally Dale wrote:
>
> [...]
> It seems like forcing project to put an assertion "Where I am".
> As our consensus, a good project is surely with "high cohesion", but never
> care "Where I am".
>
That's true and still the case.
The "Where I am?" arises fo
Hi,
I've followed your idea, it seems that go team doing this purposely.
But I don't think this is "completely reasonable".
It seems like forcing project to put an assertion "Where I am".
As our consensus, a good project is surely with "high cohesion", but never
care "Where I am".
Imagine that if
Hi,
there are two things, people might mean, when they say "fork":
a) The original meaning: Taking an open source project and adopting it,
maintaining your own changes. In this case, the forked package becomes a
different one. It has different code, maintained by different people so it
makes tota
