Hello, as Sylpheed 2.3.0 final is scheduled for 24 December according to its maintainer, it might make sense to add an ebuild for the yesterday-released version 2.3.0rc. I will attach a patch with the changes I made. These are only related to the naming of the tarball though. Feel free to improve them if needed. Regards, Milan
Created attachment 104449 [details, diff] Diff from sylpheed-2.2.10.ebuild to sylpheed-2.3.10.ebuild
I can't see why it might make sense to add an ebuild for a release candidate. If you want to help upstream with testing, just bump it in a local overlay and off you go. Akinori, your call.
Ok. Today, Sylpheed 2.3.0 has been released. For sylpheed 2.3.0 copying sylpheed-2.2.10.ebuild to sylpheed-2.3.0.ebuild is enough. (Tested successfully on x86 (hardened) and amd64.) Regards, Milan
Created attachment 104680 [details, diff] Patch for sylpheed 2.3 to replace aspell with enchant. I think that the aspell/enchant patch needs to be updated for the gtkspell use flag to be working correctly. I have attached an updated patch for 2.3 (based on the old one) which appears to work for me. Thanks, Dale
(In reply to comment #4) > Patch for sylpheed 2.3 to replace aspell with enchant. > It is not necessary to attach a patch which changed only the indent style. (The patch for 2.2 series can be applied for 2.3.0 as well) > I think that the aspell/enchant patch needs to be updated for the gtkspell use > flag to be working correctly. I have attached an updated patch for 2.3 (based > on the old one) which appears to work for me. > Why? Did you read the compose.c or the patch? It changes the behavior of Sylpheed *only* when --enable-gtkspell is passed to configure. (All changes are inside of "#ifdef USE_GTKSPELL")
Fixed in CVS. Thank you for reporting!
