Upstream is focusing in gmime-2.6 and this is the only package still depending on gmime-2.4 and without any version in the tree without gmime-2.6 support. Could you check if it works with gmime-2.6? Looking to configure.ac seems that it should work: # gmime 2.4 or 2.6? mu has only been tested with gmime-2.4, but Fedora # 14 ships with gmime 2.5.x, which registers itself (pkgconfig) as 2.6 # it is reported mu works fine with this new gmime as well, so we support # both; based on patch by GooseYArd PKG_CHECK_MODULES(GMIME,gmime-2.4,[have_gmime_24=yes],[have_gmime_24=no]) AS_IF([test "x$have_gmime_24" = "xno"],[ PKG_CHECK_MODULES(GMIME,gmime-2.6,[have_gmime_26=yes],[have_gmime_26=no]) AS_IF([test "x$have_gmime_26" = "xno"],[ AC_MSG_ERROR([ *** neither gmime-2.4 nor gmime-2.6 could not be found; please install it *** e.g., in debian/ubuntu the package would be 'libgmime-2.4-dev' *** If you compiled it yourself, you should ensure that the pkgconfig *** installation dir (e.g., /usr/local/lib/pkgconfig) is in your *** PKG_CONFIG_PATH. ])],[ gmime_version="`pkg-config --modversion gmime-2.6`" ])],[ gmime_version="`pkg-config --modversion gmime-2.4`" ]) the problem is that upstream should be contacted to either depend only in gmime-2.6 or add a configure switch to select between both versions because, otherwise, will be an automagic problem if both slots are installed and, later, gmime-2.4 is dropped (like has already being done in most major distributions) Reproducible: Always
Hi, this is preliminarily fixed with the bump to 0.9.9 of mu which supports both 2.4 and 2.6. I'll inquire with upstream for the configure switch.
Other (easier) option to upstream is to simply check for gmime-2.6 before 2.4, that way there won't be automagic problems for us as we would simply depend on SLOT 2.6 and, then, it would be used at compile time even if people have both slots installed
(In reply to comment #2) > Other (easier) option to upstream is to simply check for gmime-2.6 before > 2.4, that way there won't be automagic problems for us as we would simply > depend on SLOT 2.6 and, then, it would be used at compile time even if > people have both slots installed This is no problem. If both are installed it will link to 2.6 (already now). So, shall we make it depend on slot 2.6 and close this bug?
(In reply to comment #3) > This is no problem. If both are installed it will link to 2.6 (already now). > So, shall we make it depend on slot 2.6 and close this bug? At least in the version I reviewed (the one with snippet I provided in this bug report), it will check at first for gmime-2.4 and, then, if both are installed, it will link against it... if this situation has changed in last version, fine, simply depending on slot 2.6 will do the trick
(In reply to comment #4) > (In reply to comment #3) > > This is no problem. If both are installed it will link to 2.6 (already now). > > So, shall we make it depend on slot 2.6 and close this bug? > > At least in the version I reviewed (the one with snippet I provided in this > bug report), it will check at first for gmime-2.4 and, then, if both are > installed, it will link against it... if this situation has changed in last > version, fine, simply depending on slot 2.6 will do the trick Yes, the logic was fixed. I added the slot dep. + 06 Nov 2012; Thomas Kahle <tomka@gentoo.org> mu-0.9.9.ebuild: + Depend on gmime:2.6 per bug 439842
