On 22/05/15 15:49, Josh Matthews wrote:
https://github.com/servo/rust-harfbuzz/issues/39 is not the first request to publish certain dependencies on crates.io. I'm in favour of this; the question is whether we can build in systems that avoid the publish-and-forget workflow. Thoughts? Should we just go ahead and publish the latest revision whenever someone asks us to?
What’s the concern, that we’ll publish once and then never republish because we keep using a git dependency?
Then we can stop using a git dependency and have Servo get that package from crates.io. That way we’ll be "forced" to publish changes on crates.io before Servo can use them.
-- Simon Sapin _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo

