On 5/2/19 8:17 PM, Bruce Dubbs via blfs-dev wrote:
I've started to build gedit and it now needs gspell. I think I could
hack gedit to build without gspell, but it will probably be easier to
just add the gspell page to the book.
Building gspell is not hard, but one test fails. The offending test
says:
/* This unit test fails with the aspell enchant backend, but aspell can
* be considered deprecated, it is better to use hunspell, so WONTFIX.
* For more details, see:
* https://bugzilla.gnome.org/show_bug.cgi?id=772406
*/
aspell has been working for me for many years. Is it referenced in
the book in six places.
The question is whether it is worthwhile to update to hunspell, add
hunspell along side of aspell, or just leave aspell alone in the book.
https://github.com/hunspell/hunspell/releases hunspell-1.7.0.tar.gz
Nov 2018
http://aspell.net/ GNU Aspell 0.60.6.1 (Released July, 2011)
-- Bruce
Based off the release dates alone, I'd say let's go for Hunspell.
However, the following pages would have to be validated:
general/genlib/enchant.xml
kde/kf5/kf5-frameworks.xml
xsoft/other/thunderbird.xml
xsoft/office/libreoffice.xml
xsoft/graphweb/seamonkey.xml
We would then need to make Hunspell internal for all of those packages,
as well as preferably using system libraries in Thunderbird,
Libreoffice, KF5, and Seamonkey.
Hunspell is also maintained, and I'm not sure aspell still is. I think
it might be better to keep aspell and add Hunspell.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
