On 12/8/06, Loïc Minier <[EMAIL PROTECTED]> wrote:
We are currently in "upstream version freeze"; I think this is the last freeze before "full freeze". Following your plan requires: - a new source package (libdatrie), at least 10 days propagation to testing if everything goes fine - a new upstream version of libthai (breaks new upstream version freeze), with shlibs bumps (breaks another freeze which started longer ago, but there are not so many rdeps to libthai0), certainly 10 days at least, after libdatrie - a new upstream version of pango (breaks new upstream version freeze, has an udeb == is used in debian-installer), given the importance of pango, 10 days as well, probably after libthai This is a bit too much I'm afraid, and you didn't state any benefit at all: does it fix bugs? is it faster?
All right. That is what I also anticipated. In fact, I did plan to start the works after etch release. But the upstream release with the engine included comes so soon that I feel uncertain how this would be handled in Debian. So, I made a notice of possible alternatives for discussion, in case it's being built. Regarding the changes, the upstream engine itself has corrected some flaws about logical attribute calculation found in pango-libthai, which should be nice to backport. Regarding libthai itself, the word break engine has been replaced with a new design using external dictionary, as opposed to embarrassing, hard-coded, static data declaration in C source as done in current Debian version. Yes, this seriously breaks "upstream freeze". So, I have just held its version until etch is released.
A pango update might be feasible, it has no API change, so wouldn't need any shlib bump, but I messed with the previous update a little, and it's getting really late. I would rather backport fixes to pango-libthai if needs be.
That's fine. I'll prepare a backported fix for pango-libthai soon. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/
