Should charms have an equivalent of debian/watch?

Mark Shuttleworth mark at
Wed Jun 27 13:35:17 UTC 2012

's a rather good idea, Jorge, as long as it's a config setting
("auto-update"). As a common pattern, one config could specify a source
(stable package, ppa, version control) and another could specify whether
to auto-update. So one could have a service "running tip" that
auto-updated easily.


On 27/06/12 02:22, Jorge O. Castro wrote:
> I remember talking about this on IRC but it was only a few of us and I
> wanted to get the input from the list. Debian packages have a file
> called "watch" that watches a known upstream directory for new
> releases:
> Some charms grab tarballs from upstream and I see a few that are
> already behind, would it be a good idea for us to have an equivalent
> mechanism in charms so that we can generate a list of charms that
> might be behind? It seems to me that modifying a charm to get the
> latest minor upstream version and updating the hash and testing it
> might be a good low-barrier introduction to charms. Thoughts?

More information about the Juju mailing list