On 27 January 2014 19:28, Andy Doan <email address hidden> wrote:
> You might want to take a look at my branch. I made an update based on your comments. Specifically i think you'll want to merge in:
>
> http://bazaar.launchpad.net/~doanac/ubuntu-ci-services-itself/restish-charm-local/revision/115
194 # juju needs to know about our local charms.
195 # we could use the charms directory, but juju will wind up copying
196 # external charms we use into this directory and making our source
197 # tree dirty. using the deployer directory just makes it a bit cleaner
I don't understand what you mean by making the tree dirty. Can you elaborate?
We want to have the external charms in tree for the deployment, which
juju-deployer does. It doesn't let you bind to a specific revno, so
we'll want to have a commit or branch that builds these out with
config-manager, as we discussed this morning.
On 27 January 2014 19:28, Andy Doan <email address hidden> wrote: bazaar. launchpad. net/~doanac/ ubuntu- ci-services- itself/ restish- charm-local/ revision/ 115
> You might want to take a look at my branch. I made an update based on your comments. Specifically i think you'll want to merge in:
>
> http://
194 # juju needs to know about our local charms.
195 # we could use the charms directory, but juju will wind up copying
196 # external charms we use into this directory and making our source
197 # tree dirty. using the deployer directory just makes it a bit cleaner
I don't understand what you mean by making the tree dirty. Can you elaborate?
We want to have the external charms in tree for the deployment, which
juju-deployer does. It doesn't let you bind to a specific revno, so
we'll want to have a commit or branch that builds these out with
config-manager, as we discussed this morning.