On 22/12/15 03:52, Yehuda Katz wrote:
In my opinion, #3 is best addressed with support for automated mirroring of both crates.io and git dependencies. Mega-corps like LinkedIn use mirroring services for Rubygems, npm, and maven to ensure high-availability. This maintains the normal developer workflow and ensures that developers on the project do not rely on custom infrastructure for updates, while still ensuring that the deployment process isn't dependent on third-party infrastructure.
It's not terribly automated, but we have an internal PyPI mirror for various things that are used in the build process. My experience is that every time you have to use this it's enough pain, both in the short term and for people doing maintenance after you, that you should just put the dependency directly in-tree instead.
_______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
