Kirill A. Korinsky <kir...@korins.ky> writes: > Sebastien, > > what do you think about MODCARGO_CARGOLOCK?
ah, sorry to not responding more quickly, I looked at mitmproxy, see why you needed it... and pass on it. Globally, I still disklike it, but it resolves a real problem (due to the way upstream package mitmproxy). So I am fine with it. Regarding the documentation, I think it should mention that it do not affect the build in any way : cargo is looking at MODCARGO_CARGOTOML path only. Otherwise it could be confusing for the packager to have both. Maybe something like "used only by modcargo-gen-crates target" ? Thanks. -- Sebastien Marie
