There is a new version of the Dutch spelling (OpenTaal 1.10). For this, I created an ebuild in overlay including distfiles and I'm successfully using this for over half a year now. The new version of the Dutch spelling can be found at OpenTaal: 1. goto http://www.opentaal.org/ 2. under DOWNLOAD, click on "Instructies". Here we see version 1.10 is from 25 juli 2009. 3. under DOWNLOAD, under Instructies, click on "Bestanden downloaden". 4. The file we want is "Woordenlijst 1.10 voor Apple Snow Leopard" (do not download yet). The hyphenation file is the same as for myspell-nl-20070607 but has a slightly different licence: 1. goto http://qa.openoffice.org/issues/show_bug.cgi?id=74309 2. the file we want is the attachment hyph_nl_NL.zip (do not download yet). These files can be downloaded using wget: 1. mkdir -p /tmp/myspell-nl 2. cd /tmp/myspell-nl 3. wget http://www.opentaal.org/instructies/bestanden/doc_download/6-woordenlijst-110-voor-apple-snow-leopard 4. wget http://www.openoffice.org/nonav/issues/showattachment.cgi/66718/hyph_nl_NL.zip Now we can create distfiles for myspell-nl-20090725: 1. unzip 6-woordenlijst-110-voor-apple-snow-leopard 2. mv NL.aff nl_NL.aff 3. mv NL.dic nl_NL.dic 4. mv README_NL.txt README_nl_NL.txt 5. zip myspell-nl_NL-20090725.zip nl_NL.aff nl_NL.dic README_nl_NL.txt 6. mv hyph_nl_NL.zip myspell-hyph_nl_NL-20090725.zip 7. mv myspell-nl_NL-20090725.zip myspell-hyph_nl_NL-20090725.zip $(portageq envvar DISTDIR) We can use the ebuild from myspell-nl-20070607 for myspell-nl_NL-20090725: 1. mkdir -p /usr/local/portage/app-dicts/myspell-nl 2. cd /usr/local/portage/app-dicts/myspell-nl 3. cp /usr/portage/app-dicts/myspell-nl/myspell-nl-20070607.ebuild myspell-nl-20090725.ebuild 4. rm -f Manifest 5. ebuild myspell-nl-20090725.ebuild digest Well, that's it. I think it should be very easy to add this one to portage now.
Thanks for the version bump notice. Assigning to maintainer
Thank you for report. I wish more reports like this... :) Bumped in the tree.
You're welcome and thanx! May I ask what's the policy to get this version marked stable?
(In reply to comment #3) > May I ask what's the policy to get this version marked stable? One month in ~arch. After that if no issues found (filled in our bugzilla) open stabilization bug, set STABLEREQ Keyword and CC _only_ maintainers (found in metadata.xml and if this means nothing to you, let bug wranglers do the job :) ). After that in case maintainers think that it's Ok to stabilize package they'll CC arch teams to do actual stabilization.
