add juju-development charm

add juju-development charm

It's a charm for Juju development.

Sit back, relax, and let the juju-development charm create a first class development environment to hack on Juju.

https://code.launchpad.net/~dave-cheney/juju-core/169-add-juju-development-charm/+merge/217488

(do not edit description out of merge proposal)

[dave_cheney.net, 2014-04-28 18:17:13]

Please take a look.

[dave_cheney.net, 2014-04-28 21:56:51]

Please take a look.

[fwereade, 2014-05-06 08:38:51]

I heartily endorse the general idea, but (1) we should update the docs to
suggest using it; and (2) really, we should put it in the charm store. Any
strong reason we're not doing so? Its existence assumes network access
regardless. And if there *is* a good reason to put it in the source tree, we
should spell "repository" correctly ;p.

https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
File repostory/trusty/juju-development/config.yaml (right):

https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
repostory/trusty/juju-development/config.yaml:1: options:
can we just skip config.yaml for now?

https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
File repostory/trusty/juju-development/revision (right):

https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
repostory/trusty/juju-development/revision:1: 3
I'd prefer to skip this too.
https://juju.ubuntu.com/docs/authors-charm-components.html states that it is
"deprecated", which is a useful lie [0], but it's still pretty useless in a
local charm, and is handled by the store for store charms.

[0] the original docs explained in some detail why you shouldn't use it, iirc,
but I think it was edited for the convenience of normal humans.

[dave_cheney.net, 2014-05-06 08:45:54]

Good point. I'll figure out how to put it in a personal branch of the
charm store.

On Tue, May 6, 2014 at 6:38 PM,  <fwereade@gmail.com> wrote:
> I heartily endorse the general idea, but (1) we should update the docs
> to suggest using it; and (2) really, we should put it in the charm
> store. Any strong reason we're not doing so? Its existence assumes
> network access regardless. And if there *is* a good reason to put it in
> the source tree, we should spell "repository" correctly ;p.
>
>
>
https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
> File repostory/trusty/juju-development/config.yaml (right):
>
>
https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
> repostory/trusty/juju-development/config.yaml:1: options:
> can we just skip config.yaml for now?
>
>
https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
> File repostory/trusty/juju-development/revision (right):
>
>
https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
> repostory/trusty/juju-development/revision:1: 3
> I'd prefer to skip this too.
> https://juju.ubuntu.com/docs/authors-charm-components.html states that
> it is "deprecated", which is a useful lie [0], but it's still pretty
> useless in a local charm, and is handled by the store for store charms.
>
> [0] the original docs explained in some detail why you shouldn't use it,
> iirc, but I think it was edited for the convenience of normal humans.
>
> https://codereview.appspot.com/90860043/

[axw, 2014-05-14 09:06:06]

Handy, thanks. I'm using this to track down broken unit tests on precise without
involving The Cloud.

https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
File repostory/trusty/juju-development/hooks/install (right):

https://codereview.appspot.com/90860043/diff/20001/repostory/trusty/juju-deve...
repostory/trusty/juju-development/hooks/install:9: apt-get install -y
build-essential bzr mercurial git-core golang-go vim-nox
golang-go installs go1 on precise, which isn't sufficient for juju-core