coordinated openssl version?

[ArtemGr]

So, when one project uses a crates version of openssl and another uses a git version, the build using both projects is broken. When one project uses an upstream version and another uses a fixed version (blackbeam/rust-mysql-simple@06edff7), the build using both projects will be broken very soon.

How do we coordinate this?

rust-lang/cargo#1006 will tell us about the issue but it's little help if the issue will resurface every time somebody updates the version in one of the projects.

I'm going to open this bug in multiple projects:
blackbeam/rust-mysql-simple#7
sfackler/rust-postgres#87

[seanmonstar]

The exact version used in a specific project should be manageable via
setting the revision in the local Cargo.lock file.

On Wed, Dec 3, 2014, 11:01 PM Artem notifications@github.com wrote:

So, when one project uses a crates version of openssl and another uses a
git version, the build using both projects is broken. When one project uses
an upstream version and another uses a fixed version (
blackbeam/rust-mysql-simple@06edff7
blackbeam/rust-mysql-simple@06edff7),
the build using both projects will be broken very soon.

How do we coordinate this?

(I'm going to open this bug in multiple projects).
blackbeam/rust-mysql-simple#7
blackbeam/rust-mysql-simple#7

—
Reply to this email directly or view it on GitHub
#175.

[ArtemGr]

That doesn't work. When I change Cargo.lock and hit the build my changes in the Cargo.lock are overwritten!

For example, original: http://pastebin.com/ejcBPnru; change: http://pastebin.com/2F82hpvc; after "cargo test" the Cargo.lock becomes identical to the original one.

[ArtemGr]

@seanmonstar could hyper change its openssl dependency to use the crates version in order for Cargo to recognize that it's the same version? Steven says the semver should kick in then (sfackler/rust-postgres#87) and everything should work.

[reem]

I'm going to try and land crates.io today or tomorrow.

[ArtemGr]

Great, I'll test then!
BTW, you'd need to only update the openssl dependency for it to be compatible with mysql and postgresql drivers, the rest of them dependencies should be fine as is. Just thought I'd better mention this.

I might have made a pull request myself but I'm not that familiar with hyper's multi-crate structure.

[reem]

We'll probably use version * until things start stabilizing.

[reem]

You should just use hyper's crates.io version for now, which doesn't include the benchmarks. We are blocked from fully porting over by curl not yet being on crates.io.

[ArtemGr]

It works, thanks! Hyper is now useable alongside Mysql and Postgresql drivers.

[Manishearth]

FWIW the crates.io experience will probably be broken like this until 1.0 since library authors will have to maintain two moving targets (rather than one, post-1.0)