3 ms·
> The build may also break because of a change in an external dependency. It shouldn't unless you've been lax in how you specify your dependencies, or the libr
by ForHackernews 12y ago
> The build may also break because of a change in an external dependency.
It shouldn't unless you've been lax in how you specify your dependencies, or the library maintainers have been sloppy in what they claim for backwards-compatibility.
Obviously in the real world, both of those things happen.
- zeendo 12y agoPackage repositories go down too (Maven, RubyGems, NPM, etc...). Unless by 'lax' you mean 'didn't check in your dependencies'...I don't think I'd call that lax, though.
- ForHackernews 12y agoAt my work, we run a local mirror/proxy for dependencies. It's polite because we're not hitting those external services as frequently, and it has the advantage that we aren't reliant on them to produce builds.