Mike Hommey wrote: > > And in any case, adding a new shared lib now is too late for etch anyway > > whereas linking with hunspell can be done for etch still. > > Adding a new shared lib is too late but doing untested and unsupported > things is not. mwarf.
A shared lib is a new package and enchant, OOo etc will build against it and blocked behind it if a upload should be necessary (and those things will be linked against it) This is a difference to ice* where you just rebuildit with an improved spellchecking engine. [ If I decide to not keep libhunspell_pic.a when there's a libhunspell.so, OOo will even FTBFS currently when libhunspell_pic's gone and needs an upload, too, otherwise OOo will not, but enchant will. ] Adding a new shared library which has he potential to block RC fixes because stuff now suddenly link against that (and a upload adding the shared lib will have to go through NEW and wait 10 days and...) The hunspell patch *is* tested. I use it here on my iceweasel without problems. I of course built iceape with this patch and it seems to work fine, too. As already said, Hunspell is completely API-compatible with MySpell except the class name. The unsupported argument doesn't m ake sense either, plain Mozilla doesn't even support sharing the dictionaries between all MySpell supported apps... Hunspell itself is tested long time in unstable, both the library and the hunspell program. Hunspell's the *native* spellchecking engine in OOo since 2.0.2 (March!). OOo is not patched to support hunspell, it's the native format. enchant is a wrapper for many libs, including hunspell/myspell, calling that myspell. enchant is the proof that just rebuilding with hunspell does *not* break stuff. Interesting you ignored all mine comments in my last mail because of "Mozilla doesn't support it" even when you a) patch system-myspell in yourself b) symlink myspell/ to the shared dictionaries. Both is good, and anything else doesn't make sense for an integrated system but both are not supported by mozilla either, are they? You also seems to ignore that Hunspell is 100% compatible to MySpell. No location change, no APi change, no whatever change (except the class). And you also seem to ignore my comment that I actually did build ice* with hunspell and tried spellchecking... Gr??e/Regards, Ren? -- .''`. Ren? Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
signature.asc
Description: Digital signature
