SqurrelMail 1.4.5 spell USE flag asks for aspell, but the plugin installed uses ispell. Shouldn't this be fixed? Or if the squirrelmail spell plugin can also use aspell, at least tell users to modify it accordingly. Or even better make the ebuild make the necessary changes. Reproducible: Always Steps to Reproduce: 1. 2. 3.
No, it depends either on aspell or on ispell (with spell use flag set). If you emerge ispell, it won't ask for aspell. Neither of them works really well, to be honest, the plugin is pretty buggy.
Changing all ocurrences of ispell to aspell fixes it. Makes aspell run in compatability mode. Either way I think it should be automaticly changed if aspell is used, or at leas notify the user about the changes needed to be done.
(In reply to comment #1) > No, it depends either on aspell or on ispell (with spell use flag set). If you > emerge ispell, it won't ask for aspell. Neither of them works really well, to be > honest, the plugin is pretty buggy. Then why is it there???? Remove it and leave the option to the user to install the plugin.
(In reply to comment #3) > (In reply to comment #1) > > No, it depends either on aspell or on ispell (with spell use flag set). If you > > emerge ispell, it won't ask for aspell. Neither of them works really well, to be > > honest, the plugin is pretty buggy. > > Then why is it there???? > Remove it and leave the option to the user to install the plugin. K, we have the use flag, so we have an option, but if the package emerged is aspell, at least notify the user.
Please, read comment #1 once again. It depends *either* on aspell *or* on ispell. If you don't want aspell, then emerge ispell first and it won't ask for aspell. Period.
Closing.
