-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-02-14 01:40 PM, Rick Harding wrote: > > > On Sun, Feb 14, 2016 at 12:50 PM Aaron Bentley Yes, you can work > around this with tarfiles, but why do we want to? It's a pain to > build a tar file every time a single dependency changes. It's > easier to use S3 instead for a particular use case, but it doesn't > solve the general case. > > > I'd push back a little bit here though. We do this in a couple of > python web applications. We keep a repo of 'download-cache' which > is the current pypi .tar.gz and use that built into a single > download-cache tarball for deliver in the charms. This would be one > resource. The second resource would then be the actual python > application. It would have the makefile, requirements.txt file, > source code, etc. It would depend on the download-cache file being > there and so with the two, you'd manage both the source code and > the dependencies as two different resource files that are all > updated individually from the actual charm itself.
I would call that "working around this with tarfiles". I still think that it's more convenient to use S3 than to have to update the dependencies tarfile every time a resource changes, and I think that being less convenient that alternatives will hinder uptake. Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWwMw9AAoJEK84cMOcf+9hX3EH+gKybA2e5bWJBvCOURgv6Ep2 esVvugT7h5bW84zJUX7He+OZLM+PQV9RcWo10A+SjN3U+AVS+zgIHIlXXTDmLb4N orP8nHsgTptYuv52kNmrycASY+QDUTBrr1KhxtUjPobMO2DW4dwrbXRzWKD0U2rY 1oHH5KE6CjnRRFJGnXik6OOoP9Xskty3sOguBw9KVISjLlh4k0kl3EKRS00ED7KY PgBC/EKjD1+mLFt+TA9m+Ds6y/dSco0yWVNgbjBZ18ftxY6g4J4LCd1Sj5zXW03q Ic/iNWj3gI89dV1TGVx7VNqSex7lKS1AYODjeZC3saPcJ3oIRV97WxA7D66wRQw= =p32x -----END PGP SIGNATURE----- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
