Spec URL: http://people.redhat.com/caolanm/hunspell/hunspell.spec SRPM URL: http://people.redhat.com/caolanm/hunspell/hunspell-1.1.4-1.src.rpm Description: hunspell is the spellchecker that OpenOffice.org uses, currently it's bundled as part of OOo, this splits it out to make it available for other applications to use
So, what are the chances of actually making it so that we don't have the continued gross duplication of spell checking functionality and dictionaries between hunspell and aspell?
That's related but not quite what this mini-task is for, this is just to get the libhunspell independent of OOo, no dictionaries are included in libhunspell itself. At the moment you've got OOo, firefox and sort-of vim all hauling effectively copies of the same hunspell/myspell format dictionaries around. I say we at least split libhunspell out of OOo, then update firefox to use hunspell instead of myspell. Split the myspell/hunspell dictionaries out of firefox and OOo and put them in one place under e.g. /usr/share/hunspell The duplication of data between aspell and hunspell is still a problem, one of them needs to read the format of the other. bug 207571 relates to dictionary data proliferation
FWIW a sample dictionary src.rpm for Afrikaans would look something like... http://people.redhat.com/caolanm/hunspell/hunspell-af-0.20060117-1.src.rpm demo hunspell invocation to use above... > echo foome | hunspell -d af_ZA Hunspell 1.1.4 & foome 1 0: fooie
Release: 1 You want some %{?dist} action %package devel Requires: hunspell = %{version}-%{release} I think Requires: %name = %{PACKAGE_VERSION} is better (handles epoch too) Otherwise it looks good to me
updated spec for above comments total rpmlint output is: "W: hunspell-devel no-documentation"
Looks ok to me then.
Any reason why you're packaging the .a file? We don't normally do that unless absolutely necessary. I'll add the package, but please fix that. Please close this bug when you've built for rawhide.
all done
Package Change Request ====================== Package Name: hunspell New Branches: f-10
I assume you want a F-9 early branch here? cvs done. F-9 => what will go into F-9 deve => what will go into F-10