On Thu, Sep 27, 2012 at 8:39 PM, Eitan Adler li...@eitanadler.com wrote:
On 27 September 2012 22:52, Kevin Oberman kob6...@gmail.com wrote:
In any case, if you don't have the ispell wrapper selected, than there
should be no conflict. It looks like that was intended since there are
two
On Fri, Sep 28, 2012 at 2:26 PM, Kevin Oberman kob6...@gmail.com wrote:
On Thu, Sep 27, 2012 at 8:39 PM, Eitan Adler li...@eitanadler.com wrote:
On 27 September 2012 22:52, Kevin Oberman kob6...@gmail.com wrote:
In any case, if you don't have the ispell wrapper selected, than there
should be
I think aspell does not conflict with ispell; they have no common files.
Is it any problem with ispell when running or building aspell ?
BTW, textproc/ispell does not have CONFLICTS entry... it is confusing.
---
Tsurutani Naoki
turut...@scphys.kyoto-u.ac.jp
On Thu, Sep 27, 2012 at 6:17 PM, Tsurutani Naoki
turut...@scphys.kyoto-u.ac.jp wrote:
I think aspell does not conflict with ispell; they have no common files.
Is it any problem with ispell when running or building aspell ?
BTW, textproc/ispell does not have CONFLICTS entry... it is confusing.
On 27 September 2012 22:52, Kevin Oberman kob6...@gmail.com wrote:
In any case, if you don't have the ispell wrapper selected, than there
should be no conflict. It looks like that was intended since there are
two CONFLICTS statements. the first is unconditional and I suspect
should have been
When did this happen?
I have numerous packages that depend on ispell and numerous packages that
depend on aspell. And, a bunch that depend on both. And, they are both
installed currently.
--
Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator
For: Enterprise Server
