The installation instructions for aspell state:
"If you do not have Ispell or the traditional Unix ``spell'' utility installed on your system than you should also copy the compatibly scripts ``ispell'' and ``spell'' located in the scripts/ directory into your binary directory which is usually /usr/local/bin so that programs that expect ispell or spell command will work correctly."
This is not done by the ebuild, resulting in an error message when attempting to check spelling in kmail (which tells you to install aspell or ispell).
Steps to Reproduce:
1. Open new message in kmail.
2. Type an email with spelling mistakes.
3. Select Tools | Spelling
(This will probably only manifest itself when ispell and spell aren't installed).
Error message stating:
"ISpell/Aspell could not be started. Please make sure you have ISpell or Aspell
properly configured and in your PATH."
Should have checked the spelling.
The relevant scripts are in the aspell distribution, all that needs to be done
is copy them in when installing.
ok, I'll figure something out for this
dictionary team, thoughts on exorcising ispell from the tree entirely?
are we sure that ispell is not used anymore? i'm very skeptical that nuking them would be a good idea.
we could do this as a pkg_postinst() for both ispell and aspell using the alternatives eclass.
any chance that kmail has some other way to determine which spell checker to use?
I cannot reproduce this error with kmail from KDE 3.3.
This is with
and no ispell installed (I also have no spell or ispell in my path).
The spellchecker library was rewritten for KDE 3.3 (now kspell2 instead of kspell). That probably fixed the detection issues with aspell.
Check bug #67748. The problem is that new ebuilds of aspell create /usr/lib/aspell-[version] and kde still looks after /usr/lib/aspell/. Creating a link solves the problem, although somewhat ugly solution.
Ricardo can you confirm that rebuilding kdelibs doesn't fix this (see bug #67748)?
Also aspell-0.6 has only been in the three for a couple of months so I don't think its the problem.
Since #67748 is fixed lets close this also.