2018-04-18 18:42 GMT+03:00 Laurent Bigonville <bi...@bigon.be>: > On Tue, 5 Sep 2017 13:12:25 +0300 Timo Jyrinki <t...@debian.org> wrote: >> There are also new 2.0.0 and 2.1.0 releases now, Enchant being actively >> developed again. > > What's are the plans for enchant?
I think no plans (time/resources) known at the moment, but the path would be clear for someone to pursuit. Prach made enchant LowNMU so it'd be easier now for anyone to hop in. > I see that enchant 2.1.2 has been packaged in experimental. > > The transition involves quite some packages > (https://release.debian.org/transitions/html/auto-enchant.html), Timo did > you try to do an archive rebuild? to see existing packages can use version 2 > of the library? do you know if the porting effort is big? I only tested rebuilding some and reported on debian-devel https://lists.debian.org/debian-devel/2018/01/msg00178.html > Any reasons why libenchant2 has Breaks/Replaces with libenchant1c2a and are > not co-installable? That was probably just before it became possible to package enchant2 as a separate source package for parallel installation, and it should now be allowed. So the path forward would be to use Tim's excellent enchant2 work, but before that a newer snapshot of the gnulib [1] should be packaged. [1] https://tracker.debian.org/pkg/gnulib -Timo
