Juju feedback from the Launchpad Yellow Squad

Gustavo Niemeyer gustavo.niemeyer at canonical.com
Thu Feb 16 03:12:26 UTC 2012

> That is nice if your hook is written in shell.  If you hook is written in another language, such as Python, you may want helpers to do this beyond, for instance, subprocess.call.  We did, in order to make error handling behavior that we thought was better in a juju context--and even to keep us from needing to remember to use "-y --force-yes" in our apt-get install.
> If you want helpers to do bootstrapping, they themselves need to be bootstrapped.  The metadata approach to getting initial packages installed gives you that.

To be clear, I'm not against putting package information in the
metadata, as long as we support that properly. We already had plans
for that since the early days. What I'm against is having helpers that
need themselves to be installed and run, and understood by the user as
well, and maybe debugged. If we there are reasons why we need to put
fundamental things like packages and repositories in the metadata,
let's talk about it, spec out, and implement into juju proper, so that
all the user gets is a trivial "use this in your metadata" comment.

Gustavo Niemeyer

-- I'm not absolutely sure of anything.

More information about the Juju mailing list