I've reviewed the changes myself as well, making some small corrections along the way: da124c7
Two things that I do not understand yet:
libalpm/src/event.rs -- why was _Unknown deleted?
libalpm/src/package.rs -- why was _ => panic! deleted?

OK, so the native tests pass now. Need to make docker work now.

TBH I'm slowly starting to give up on docker for "alpm-sys".. It doesn't even have any tests. It only tests compilation, which is checked with a local cargo publish anyway.
(Note though that all non-docker tests work fine now.)

The appropriate way, it seems, would be to e.g. create a Dockerfile. But haven't touched docker for quite a while.

Thoughts?

Hi - sorry this is quite a big patch. I need to go through it all.

@derekdreery yes, I understand. Took a considerable effort for me to do it as well.

@derekdreery any news? If we can drop off testing in Docker for now, it'll be sad of course, but then again we wouldn't have to maintain the fork for now. Testing in docker could be added back later I guess, if libalpm starts compiling on stable Rust and somebody would be interested...

Not sure of course. Thoughts?

This is a very large patch, and I don't really have time to review. I recommend forking this project, and making a new crate on crates.io.

I will try to review if I get some time in the future, but I don't know when that might be.

@derekdreery would you prefer to fork the project on cargo/crates as well?

I've done it here in Nov 2018 https://crates.io/crates/libalpm-fork because I've needed a newer version. Should it remain a fork on crates.io or you'd prefer to merge instead?

By the way, I didn't tell it explicitly, but I'm using the project in an AUR helper that I'm building: https://github.com/vn971/rua
So kudos for the project, it really does help 👍 !