1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
juju-core
=========
juju is devops distilled.
Getting started
===============
`juju-core` is written in Go (http://golang.org), a modern, compiled, statically
typed, concurrent language. This document describes how to build `juju-core`
from source. If you are looking for binary releases of `juju-core`, they are
available from the Gophers PPA, `https://launchpad.net/~gophers/+archive/go`.
Installing Go
-------------
If you are using Precise or later, the `golang-go` package is available in the
main archive and can be installed with
sudo apt-get install golang-go
Using Go compiled from source is also supported, but not covered in this document.
Setting GOPATH
--------------
When working with the source of Go programs, you should define a path within
your home directory (or other workspace) which will be your `GOPATH`. `GOPATH`
is similar to Java's `CLASSPATH` or Python's `~/.local`. `GOPATH` is documented
online at `http://golang.org/pkg/go/build/` and inside the `go` tool itself
go help gopath
Various conventions exist for naming the location of your `GOPATH`, but it should
exist, and be writable by you. For example
export GOPATH=${HOME}/work
mkdir $GOPATH
will define and create `$HOME/work` as your local `GOPATH`. The `go` tool itself
will create three subdirectories inside your `GOPATH` when required; `src`, `pkg`
and `bin`, which hold the source of Go programs, compiled packages and compiled
binaries, respectively. You should add `$GOPATH/bin` to your `PATH`.
Setting `GOPATH` correctly is critical when developing Go programs. `GOPATH`
should be exported as part of your login script. You can check your `GOPATH`
with to `go` tool itself.
% go env | grep GOPATH
GOPATH="/home/dfc/work"
Other prerequisites
-------------------
A number of additional prerequisite packages are required to compile `juju-core`
and run the tests.
sudo apt-get install mongodb build-essential bzr zip git-core
Getting juju-core
=================
The easiest way to get the source for `juju-core` is to use the `go get` command.
go get -v launchpad.net/juju-core/...
This command will checkout the source of `juju-core` and inspect it for any unmet
Go package dependencies, downloading those as well. `go get` will also build and
install `juju-core` and its dependencies. To checkout without installing, use the
`-d` flag. More details on the `go get` flags are available using
go help get
At this point you will have the bzr working copy of the `juju-core` source at
`$GOPATH/launchpad.net/juju-core`. The source for any dependent packages will
also be available inside `$GOPATH`. You can use `bzr pull`, or the less convenient
`go get -u launchpad.net/juju-core/...` to update the source from time to time.
If you want to know more about contributing to `juju-core`, please read the
`CONTRIBUTING` companion to this file.
Building juju-core
==================
go install -v launchpad.net/juju-core/...
Will build juju and install the binary commands into `$GOPATH/bin`. It is likely
if you have just completed the previous step to get the `juju-core` source, the
install process will produce no output, as the final executables are up-to-date.
Using juju-core
===============
After following the steps above you will have the `juju` client installed in
`GOPATH/bin/juju`. You should ensure that this version of `juju` appears earlier
in your path than any packaged versions of `juju-core`, or older Python juju
commands. You can verify this using
which juju
--upload-tools
--------------
The `juju` client program, and the juju 'tools' are deployed in lockstep. When a
release of `juju-core` is made, the compiled tools matching that version of juju
are extracted and uploaded to a known location. This consumes a release version
number, and implies that no tools are available for the next, development, version
of juju. Therefore, when using the development version of juju you will need to
pass an additional flag, `--upload-tools` to instruct the `juju` client to build
a set of tools from source and upload them to the environment as part of the
bootstrap process.
juju bootstrap -e your-environment --upload-tools {--debug}
|