New version of gmime, with mono bindings. Needed for Beagle. I have attached an ebuild for it -- basically the same as 2.1.9, with new IUSE and one extra line for econf. Built successfully on x86, so I've left that as the KEYWORD, whilst changing the others to ~. If that's not the correct thing to do, please tell me. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 48277 [details] Ebuild for gmime-2.1.10
Actually, our ebuild policy says that version bumps have to be marked unstable on all keywords previous version had. Moreover, there's a typo in provided ebuild - use_enabled instead of correct use_enable. That said, I'm testing the ebuild as we speak.
Ah, oops! It seems that the tarball does autodetection, so the fact that it failed just meant that everything happened as expected... Thank you for clearing up the KEYWORD problem.
Ok, found another bug - gmime also needs gtk-sharp installed: checking for gtk-sharp >= 0.91.1... Package gtk-sharp was not found in the pkg-config search path. Perhaps you should add the directory containing `gtk-sharp.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk-sharp' found When determining dependencies for a package, it is a good idea to look in configure.in (or .ac).
Ah, good pointer. I'll remember that.
Hm, and as dev-dotnet/gtk-sharp doesn't have any amd64 keyword, we'll have to drop amd64 from gmime for the time being. I'll fill a bug to amd64 team to test these packages and add their keyword as appropriate.
InCVS now, thanks for the ebuild.
