Subordinates feel a bit heavy weight for this purpose, a simple alternative is to just pass the vs the vcs config string through to a generic vcs tool like mr (apt-get install mr, http://joeyh.name/code/mr/ docs are mostly in the cli help and man).. and then just mr checkout vcs_url / mr update vcs_url
-k On Fri, Nov 8, 2013 at 4:52 PM, Jason Hamilton <[email protected] > wrote: > So, I've been browsing the charms lately and it looks like a lot of charms > use a VCS (git, bzr, svn, etc). When I have been designing charms, I like > to pull from a VCS and I prefer Git. I realize that the charms I want to > use don't have a Git options. Also the charms I make, I only offer Git. > So my thinking is that it would be nice to create a VCS relationship that > allow a service create a subordinate VCS charm, which pulls from a > repository and updates it. The parent charm can just expose a folder to > pull to. I really think this would help with the modularity of the charms. > > > Take for example the LAMP charm. It only uses Bzr for its repo. What if > it just required a VCS charm, that way I can use whatever I want (git, bzr, > svn, ftp, http, S3, etc). Is there anything like this already? What do you > think about this? Any feedback would be appreciated. > > Jason > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
