Jay,
I think you're touching on some important topics. Tuning and optimizing
charm installation without fetching tons of extra packages around an
install is certainly something I'm very open to experimentation with.
This particular merge makes me suggest we run this through the gauntlet of
I have to disagree slightly, currently (and thankfully?) the current way
most charm-helpers aim to be included in charms is by embedding a working
snapshot of that version of charm-helpers. So merging this wouldn't affect
a huge number of charms, instead maybe the 5 or 6 at most that download
from
Reiterating my comment on the MP, I agree with Marco that, due in part
to the fixed-point usage pattern of charm-helpers and in part to the
specifics of the change, I don't see it as having much potential for
breakage.
That said, I'm certainly not against testing it before merging.
On Thu, Nov
Greetings,
I wanted to bring attention to a pending MR
https://code.launchpad.net/~evarlast/charm-helpers/use-no-install-recommends/+merge/242270
which I feel can help charm-helpers.
By not installing recommended packages, charms will install packages
faster, with less unneeded packages.
This
