Hi all,
(cross-posting to juju & juju-dev)
I've created a tool / library for organizing and managing resources
(binary blobs, tarballs, Python packages, and, eventually, apt
packages) required by a charm. The idea is to be an interim tool, and
a test-bed for the resource features that have been
Per request, the documentation is now also available on
ReadTheDocs.org: http://jujuresources.readthedocs.org/
On Wed, Feb 11, 2015 at 11:25 AM, Cory Johns wrote:
> Hi all,
>
> (cross-posting to juju & juju-dev)
>
> I've created a tool / library for organizing and managing resources
> (binary blo
Hi Cory,
While it's fine and welcome to have such test bed features, it feels
like the proposal and implementation have quite different goals from
the actual resources feature we've been talking about for a while, so
as a very early suggestion and request, I would strongly recommend
renaming the f
Gustavo,
Can you be more specific on how it differs from the goals of resources
streams? As I mentioned in my first email, I asked around to try to
get specific information about the proposed feature and wasn't able to
get any concrete answers or documentation. So I created this based on
what I
I can, but that's not the right way to proceed if you were in fact
trying to implement an important feature of juju that was extensively
discussed.
1. The project has a technical lead and a manager which should have
the proper information to bootstrap this, or at least know who to talk
to.
2. The