Closed vhdirk closed 6 years ago
I not against adding GMime-3.0.gir
to gir-files as long as it can normally regenerated,
but IMHO this gmime-sys need separate repo or included in https://github.com/vhdirk/gmime-rs as we do for cairo
I can include this in gmime-rs (I'll have a look at cairo). That may also make it easier for me to develop it, since maintaining 3 repos is a bit of a hassle.
I'm moving this to the main gmime-rs repo: https://github.com/vhdirk/gmime-rs. That's actually far easier to maintain. Any conrtibutions would be more than welcome! (How do you do a pull request for an entire repo?)
How do you do a pull request for an entire repo
Same as this PR ;) Or you meant something different?
I meant that at some point the gmime-rs repo could be eligible for moving into the gtk-rs namespace?
Well gmime
seems works in Windows too.
So I don't see big problem with transferring when it ready.
@GuillaumeGomez, @sdroege what you think about this?
Are we talking about a repository or a type?
About repo
I don't really have an opinion. Go for it if someone wants to maintain it :)
Is anybody actually still using gmime, is it still maintained? Is there maybe a nicer Rust-only solution?
Not sure if it's still actively maintained. I think Geary uses it? I was considering a rust-only solution for a mail client I'm building, but the eco system in that aspect is still rather lacking. GMime seems far more capable. I'm not sure if I'll be able to maintain it in the long run, but gmime seems to evolve really slowly, if at all.
I've been working on bindings for GMime.
Currently, the gmime-sys crate builds, and allows the top-layer crate (https://github.com/vhdirk/gmime-rs) to build against it.
Even though this PR is currently not suitable for merging. What needs to be done in order for it to get merged?