doc/index.html: update/fix Tails instructions

[leif]

I just tested on Tails 1.3 and found that while the instructions result in a
working Pond (with GUI) they also result in a .bashrc that prints these two
errors in every new shell:

unexpected EOF while looking for matching `''
syntax error: unexpected end of file

One of the aliases (pond) was still set, but the others (pond-build, pond-cli,
pond-install-deps) are not set. I'm not sure how this could've happened as I do
remember testing the .bashrc before. Anyway, this commit fixes the instructions
so that the aliases get saved properly.

[leif]

Oops, I totally lied - I actually tested in Tails 1.2.3, not Tails 1.3. Having now actually tested in Tails 1.3 I can report that they've removed the HTTP proxy and go get is now broken. I'll open a new pull request soon.

[sycamoreone]

@leif just some comments and questions:

• Wouldn't it be easier to use Tails' Additional Software feature instead of manually installing the dependencies using an alias? Or should this wait until the feature isn't marked as experimental anymore in Tails?
• GOPATH isn't needed to run Pond and could be removed from .bashrc saving a line or two in the instructions. (See also Fix RUNNING information. #163)
• What do you mean with "they've removed the HTTP proxy"? Is the problem the same as the one described here Tails and unrecognized path errors xmpp-client#82? (I haven't had time to investigate the best solution there, and I am quite certain that the problem is the same.)

[sycamoreone]

Another note: When the golang.org/x import paths are used instead of code.google.com/p, then mercurial also isn't needed anymore, so one packet less has to be installed.

[leif]

Wouldn't it be easier to use Tails' Additional Software feature instead of manually installing the dependencies using an alias? Or should this wait until the feature isn't marked as experimental anymore in Tails?

Yeah that looks like a good idea. I haven't tried the Additional Software feature yet.

GOPATH isn't needed to run Pond and could be removed from .bashrc saving a line or two in the instructions. (See also #163)

Good point.

What do you mean with "they've removed the HTTP proxy"? Is the problem the same as the one described here agl/xmpp-client#82? (I haven't had time to investigate the best solution there, and I am quite certain that the problem is the same.)

They've completely removed polipo, the HTTP proxy which previously made lots of things work including go get. For more info you can look at the other related tickets mentioned in the Tails changelog.

Anyway, as I just wrote on the xmpp-client ticket, while investigating this I noticed that go get actually falls back to HTTP when HTTPS connections fail (!!!) so it appears that go get isn't actually a safe command to run over tor (or any untrusted network). I'm very disappointed in go right now :(

[leif]

The current best instructions for installing pond on Tails can be found in pull request #187