On Wednesday, 20 December 2017 4:44 AM, Gianfranco Costamagna wrote: > https://codesearch.debian.net/search?q=freetype-config
> this is a big no-go, first, please ask Steve to review, but I would assume > this patch > is wrong, because a lot of packages are right now calling freetype-config in > their build > script. 33 reverse build dependences FTBFS after the removal of freetype-config. 11 don't care, and 42 already use pkg-config to detect freetype2. freetype-config is a wrapper for pkg-config if the latter is installed. Unfortunately, this outputs the wrong libdir when cross-compiling. This is also the case when using the autoconf-detected path via the 'else' block. > (in libpng1.6 we kept it with removing of the multi-arch bits, to make it > have the same > md5sum across multiple architectures). > See: > https://sources.debian.org/src/libpng1.6/1.6.34-1/debian/patches/libpng-config.patch/ This has possibilities, since Debian searches /usr/lib and /usr/lib/<triplet>, skipping incompatible libraries. I can't find the thread immediately, but I remember a similar proposal being rejected in favour of cleanly removing freetype-config. Ultimately, the goal is to enable multi-arch support in libfreetype6-dev. That can probably be achieved with or without freetype-config. Hopefully Steve can give us some guidance on how to move forward.
