osx client

Mark Mims mark.mims at canonical.com
Mon May 14 19:29:23 UTC 2012


On 05/14/2012 01:08 PM, Gustavo Niemeyer wrote:
> On Mon, May 14, 2012 at 3:33 PM, Mark Mims<mark.mims at canonical.com>  wrote:
>> imbrandon added a github project ( http://jujutools.github.com/ from
>> http://github.com/jujutools) for homebrew-juju, the osx juju cli packages.
>>
>> correction this repo is just a packaging formula... it pulls the juju cli
>> itself from lp:juju but the remaining arguments still apply
> What's the problem we're trying to solve, more precisely?  Brandon has
> been doing a great job on the MacOS front, and I'm concerned about
> arbitrating anything around it that could disrupt the good flow that
> is happening. I'd prefer to hear from him what he'd like from us to
> support his efforts.
excellent point... thanks for the great work Brandon!

I'm just asking this now because I'm concerned about too many things 
living in too many places for us to maintain properly.  The pull request 
notifications and bugs for the brew packages come through a separate 
channel from even the mp notifications and bugs for the similar lp build 
recipes.

We start adding up juju distro, juju ppa, juju build recipes, 
github.com/jujutools, lp:charm-tools, lp:juju-jitsu, lp:charms, 
github.com/charms, and we have to start building custom views on top of 
all this to just get the current state of the ecosystem.

Do existing projects, such as openstack, have tools we can use to help 
with this problem?

>
>
> gustavo @ http://niemeyer.net
>


-- 
Mark Mims, Ph.D.
Canonical Ltd.
mark.mims at canonical.com
+1(512)981-6467




More information about the Juju mailing list