Split `src/purple` out into a crate?

[lupine]

I have a C-based libpurple protocol plugin for Delta Chat. At some point, Delta rewrote itself from C -> Rust, and since discovering the purple-sys crate, I've decided to rewrite my own plugin in Rust.

In this repository, src/purple looks to be a safe wrapper on top of purple-sys. It (and purple-icq generally) looks like a better example to follow than using purple-sys directly in the way pidgin-wechat does. Thanks for putting it together.

Since my plugin is GPL as well, I can just copy the useful code, but I was wondering if you'd consider publishing it as a separate crate, to make it easier to manage dependencies and contributions back? It would also improve discoverability!

It looks like we've also both forked purple-sys itself. You might be interested in integrating these changes into your branch of that as well, if you decide to split out src/purple - sbwtw/libpurple-rust#3

My project is purple-plugin-delta if interested; the rust branch is where I'll be working on the new implementation until it has feature parity.

[aviau]

This was on our to-do list, but now that there is interest we may look into doing that faster. cc @isra17

[lupine]

Great to hear! I've already started accumulating changes to my local copy of src/purple, but I'm making an effort to keep them logically separated and will submit them upstream once it's split out :)

[isra17]

I did the split and published crates, see #47

[lupine]

Thanks for that! I've opened some PRs against the purple-rs crate.

I've also created a next branch in my fork which is the result of merging all three, and reworked https://code.ur.gs/lupine/purple-plugin-delta/src/branch/rust to use it. Looks good so far :D : https://github.com/lupine/purple-rs/tree/next