On Tue, Jan 13, 2009 at 12:40 PM, Harshula <harsh...@gmail.com> wrote: > Hi, > > On Wed, 2008-12-31 at 23:59 +0800, LI Daobing wrote: > >> libm17n-dev already ships the .pc files, so the .la files should no longer >> shipped. check more information in >> http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html >> >> $ dpkg -L libm17n-dev | grep la$ >> /usr/lib/libm17n-core.la >> /usr/lib/libm17n-flt.la >> /usr/lib/libm17n-gd.la >> /usr/lib/libm17n-gui.la >> /usr/lib/libm17n-X.la >> /usr/lib/libm17n.la >> /usr/lib/m17n-lib/libmimx-anthy.la >> /usr/lib/m17n-lib/libmimx-ispell.la > > Are you referring to: > > "Removing .la files and replacing them by pkgconfig files remove the > requirement. However, the transition needs to be coordinated in > leaf-first order, or will cause problems found in libXcursor and > libXrender. Bug# 363239 and Bug# 363057." > > Are you saying there are no leaf-nodes depending on libm17n-dev that > require libtool support? > currently only 4 packages (except libm17n itself) depends on libm17n-0:
1. mgp: use m17n-config --cflags and m17n-config --libs 2. mlterm-im-m17nlib: use m17n-config --cflags and m17n-config --libs 3. scim-m17n: use pkg-config 4. uim-m17n: use pkg-config and only the "m17n-config --libtool" will use the "*.la" file, so maybe it will be safe to build these packages after libm17n-dev remove the .la files (need test). there are 1 package depends on libm17n-dev 1. uim-dev: this one ship 3 .la files but no one contains m17n issues so it is also OK for this. hope these information can help you. :-) -- Best Regards, LI Daobing -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
