On 6/20/20 3:35 PM, Adrian Bunk wrote:
> icu-config is no longer available on Debian/Ubuntu, for background
> see https://bugs.debian.org/898820
Is it worth pointing out that Debian/Ubuntu are becoming real PITAs?
>From the bug:
libicu-dev is not multi-arch aware, causing the i386 version to conflict
with the amd64 one which makes it impossible to install both. As a
result the /usr/lib/i386-linux-gnu/libicu*.so symbolic links are missing
so that developing 32 bit applications using this library is impossible
on a 64 bit system.
Fedora handles this problem /just fine/:
$ grep libicu-devel /var/log/rpmpkgs
libicu-devel-63.2-3.fc31.i686.rpm
libicu-devel-63.2-3.fc31.x86_64.rpm
$ ls -l /usr/bin/icu-config*
-rwxr-xr-x 1 root root 205 May 28 2018 /usr/bin/icu-config
-rwxr-xr-x 1 root root 22011 Jul 25 2019 /usr/bin/icu-config-32
-rwxr-xr-x 1 root root 22019 Jul 25 2019 /usr/bin/icu-config-64
$ rpm -qf /usr/bin/icu-config*
libicu-devel-63.2-3.fc31.x86_64
libicu-devel-63.2-3.fc31.i686
libicu-devel-63.2-3.fc31.i686
libicu-devel-63.2-3.fc31.x86_64
The main script is a 32/64-bit selector script which then calls the
right arch-specific binary, and the relevant symlinks are all correct in
/usr/lib{,64}.
Not that I'm interested in a distro war, but some of us are getting
darned tired of Debian/Ubuntu's high-handed /purity/ demands, virtually
demanding that everyone else fall over for them.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
