dependence error of loveoneanther.at about tiedot

[HouzuoGuo]

What actions did you take before seeing this error?

[tonyw]

just run like this:
go get github.com/HouzuoGuo/tiedot
----- Original Message -----
From: Howard Guo [email protected]
To: HouzuoGuo/tiedot [email protected]
Cc: wangxin [email protected]
Subject: Re: [tiedot] dependence error of loveoneanther.at (#16)
Date: 2013-08-04 15:17

What actions did you take before seeing this error?

—
Reply to this email directly or view it on GitHub.

[HouzuoGuo]

Fixed in commit 7308d7d

Please use go get loveoneanother.at/tiedot rather than getting from github. Sorry!

[tonyw]

in that case,how to hack the source code,if I want to do something myself.In this way,it mean you reject any others pull request.

[HouzuoGuo]

thank you for the feedback, that's a totally valid point, let me have a think about it.

Do you know how other Go projects resolve similar issue?

[tonyw]

why not rename package loveoneanther.at to github.com/HouzuoGuo ? Any other think of?

[HouzuoGuo]

Thank you.

This project was initially a programming exercise, so I chose to use my own domain name space, which gave me a good exercise on Go project hosting.

My dev setup uses standard Go directory structure, it looks like this:

go-workspace/
    src/
        loveoneanother.at/
            tiedot/
                (git repository lies here)

I am looking at some other Go projects see how they tackle this difficulty.

[tonyw]

This path structure sounds like Java style,not go style.an easy way is create a shell for that.like

ln -s ../../loveoneanother.at ../../HouzuoGuo
export GOPATH=../../../
go build

[HouzuoGuo]

Please educate me if I misunderstood http://golang.org/doc/code.html
I thought a repository has to be kept and managed inside a workspace. Although it may be easier for a contributor to clone an entire go workspace, but in that case a normal user will not be able to import the repository itself - go cannot import a workspace.

[tonyw]

I am also a new one ,In go world.the oolang's author create the shell-tools(go get) for dependence management easily.
Also you can import your private repository without shell-tools(go get).but you have to manage dependence yourself.
So in that case the coder have to create some tools(please my pull request for this) for that.
Golang is too young and there are no good solutions for dependence(third party package and package's version).So golang's author said sometime's have to do "copy-code-to-there" for reduce dependence.
Anyway,the tiedot is a seperate application,no care of other's projects dependent on.
and go
在 2013-8-6，上午7:12， Howard Guo 写道：

Please educate me if I misunderstood http://golang.org/doc/code.html
I thought a repository has to be kept and managed inside a workspace. Although it may be easier for a contributor to clone an entire go workspace, but in that case a user may be unable to import the repository.

—
Reply to this email directly or view it on GitHub.

[HouzuoGuo]

I see, that's a good point indeed.
How about we create a script for those who have git cloneed tiedot, and automatically put the repository inside user environment's go workspace?

Something like:
(assume pwd is tiedot.git)

[ "$GOPATH" != "" ] && mkdir -p $GOPATH/src/loveoneanother.at/tiedot && cp -R ./* $GOPATH/src/loveoneanother.at/tiedot

[HouzuoGuo]

In this commit c48403c, I added an INSTALL file to inform user the proper way of cloning this repository.