4 ms·
I'm a bit confused as well, unless you're referring to "installing libs at any version except HEAD", in which case I vehemently disagree with you. Deterministi
by Groxx 10y ago
I'm a bit confused as well, unless you're referring to "installing libs at any version except HEAD", in which case I vehemently disagree with you. Deterministic builds are a must-have for production systems.
- icebraining 10y agoThe question is whether that should be included in the project, or as a configuration of the deployment tool.
- yxhuvud 10y agoThere is no question. If it isn't included in the project, then any errors you get are not repeatable.
- icebraining 10y agoWhy can't you get the versions in question from the origin of the error (deployment config if it's an internal error, or asking the user if it's an external report)?
- yxhuvud 10y agoIt is certainly possible, but adding a manual step for something that has no reason not to be automatic doesn't make sense. Yes, you can certainly choose to do more manual work for no reason, but why would you? And if you don't want that (for example if you distribute a library), you can still distribute the project without the lockfile, and then have the users distribute the lockfile back to you to get a repeatable error.