3 ms·
Checking in your deps handles that. If your tests don't pass, don't check in the change. But this requires source control systems that can store the files for
by skybrian 12y ago
Checking in your deps handles that. If your tests don't pass, don't check in the change.
But this requires source control systems that can store the files for many projects at a time. (See today's other discussion about git.) [1]
[1] http://bitquabit.com/post/unorthodocs-abandon-your-dvcs-and-return-to-sanity/# http://bitquabit.com/post/unorthodocs-abandon-your-dvcs-and-...
- pbh101 12y agoDepending on specific versions of dependencies should also handle that, without needing to check in all dependencies. This is the approach generally taken when using Maven and related tools.
- nulltype 12y agoThe only difference is that finding the dependencies can be a pain if they changed location, or github is down, or the specific version isn't a specific git commit or something like that. Since there's no real difference, it doesn't really matter if you check in deps or have specific versions in a config file, either solution solves the underlying problem of having non-precise dependencies (i.e. just a github repo, or a version selector like >= 2.6)