PPAs for juju api client and deployer

[Marco Ceppi]

I guess that was my question. I'd really like to simplify the user
experience when installing and managing Juju tools, having all the
additional tools like deployer, charm-tools, amulet, etc in one place would
be a nice step forward. I've just used ppa:juju/pkgs as it was *the* canonical
ppa for juju packages back in the pyjuju days. Ultimately, deciding where
these tools should live, using that ppa, then documenting it for users in
my opinion is the way to go. So whether that ppa is juju/pkgs or a new one
like juju/tools is fine, I think we just need to decide.


On Wed, Jul 24, 2013 at 8:48 PM, Andreas Hasenack <andreas at canonical.com>wrote:

> On Wed, Jul 24, 2013 at 9:45 PM, Marco Ceppi <marco.ceppi at canonical.com>wrote:
>
>> Hi Andreas!
>>
>> Thanks for getting this packaged! I wonder in general though, would it be
>> better to place it in ppa:juju/pkgs to avoid having to add too many ppas to
>> peoples machines?
>>
>>
> Maybe, I don't know. It's trivial to change the target PPA in the recipe.
>
> Isn't ppa:juju/pkgs the old python juju ppa?
>
> launchpad.net/~juju has many PPAs, are all current or should some be
> deprecated?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130724/eef5f1b0/attachment-0001.html>