If enchant hasn't been built with USE=aspell, opening a compose/reply window gives this error: Spell checker could not be started. Couldn't initialize en_CA dictionary: (null) Couldn't initialize en_CA speller. The options to choose the default dictionary in preferences are also greyed out.
Thanks for that information, fixed in tree for all revisions of 3.6.1 (not with EAPI=2 as I plan to stabilise -r1).
Editing stable ebuilds for non trivial changes is unsupported, and we have a broken ebuild now. Adding the report as depend.
That is because only ~arch enchant has IUSE "aspell", stable enchant IUSE is "".
built_with_use --missing true I got that implemented for a specific reason.
Fixed along with 250573. Diego, your solution was right
2008.0/desktop profile has USE spell enabled by default, but enchant's default USE flag is for hunspell which makes the build die by default to the check.. valid or not. If claws-mail really needs aspell, why is the USE flag called spell? To annoy users?
(In reply to comment #6) > 2008.0/desktop profile has USE spell enabled by default, but enchant's default > USE flag is for hunspell which makes the build die by default to the check.. > valid or not. Yes, but users request spell-checking abilities not using the aspell program. > If claws-mail really needs aspell, why is the USE flag called spell? To annoy > users? No, to give them what they requested. But the more I think about it, I suspect a configuration failure on dirtyepic's system. Ryan. Do you have en_CA dictionaries installed for hunspell? If not, please do so and try again. app-dicts/myspell-en should be suited for you.
(In reply to comment #7) > Ryan. Do you have en_CA dictionaries installed for hunspell? If not, please > do so and try again. app-dicts/myspell-en should be suited for you. This exactly was the problem, so the USE flag check is not needed at all, if enchant is correctly configured. Sorry for the whole confusion, but I relied on dirtyepic too much without enough checking on my own. Samuli, if you had discussed the issue with me or any other maintainer we maybe would have found the correct solution earlier. Closing this as INVALID.
ah hell, sorry about that. i didn't make the connection between hunspell and myspell. drac, USE flags control functionality, not what library is used. spell is appropriate.
(In reply to comment #9) > drac, USE flags control functionality, not what library is used. spell is > appropriate. (In reply to comment #8) > This exactly was the problem, so the USE flag check is not needed at all, if > enchant is correctly configured. Sorry for the whole confusion, but I relied > on dirtyepic too much without enough checking on my own. It's fine now if the "useless" built_with_check is gone to call it "spell". It was the check that made me trust Opfer's judgement that aspell is required. Thus I wanted it changed to "aspell" so user(s) can just set "aspell" in make.conf's USE and be done with it instead of package.use / profile hassle. But that's all obsolete now. > Samuli, if you had discussed the issue with me or any other maintainer we > maybe would have found the correct solution earlier. > Closing this as INVALID. True to that.
*** Bug 256564 has been marked as a duplicate of this bug. ***
