I upgraded to the 17.1 dev profile and noticed net-im/telegram-desktop-bin-1.6.7 installs to /usr/lib instead of the preferred /usr/lib64. Telegram still works fine though. $ file /usr/lib/telegram-desktop-bin/Telegram /usr/lib/telegram-desktop-bin/Telegram: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=52f7d3235ff06b783db1432527790a15aad9fb9b, stripped $ emerge --info net-im/telegram-desktop-bin net-im/telegram-desktop-bin-1.6.7::gentoo was built with the following: USE="" ABI_X86="(64)"
Well the file is actually a stand-alone binary, which only takes a few shared libraries. So from a functional point of view it does not matter much where you place it. On my 17.0 profile /usr/lib is a symlink to /usr/lib64 so the file actually resides in /usr/lib64/. I assume that on i386 i would see a symlink to /usr/lib32 or there would not be another variant. So the ebuild works without making a difference. I do not know whether 17.1 would work differently. If so the ebuild could probably switch the destination depending on the arch.
/usr/lib64 is not 'preferred'. /usr/lib is the correct place for stand-alone software packages.
Just to clarify the WONTFIX, things did not change with profile 17.1? So the ebuild is fine and /usr/lib will always take care of arch difference (i.e with symlinks) as i expected for 17.0?
There's no arch difference since you will be only installing one version of it.
