Summary: | net-im/telegram-desktop-bin installs /usr/lib/telegram-desktop-bin/Telegram outside LIBDIR | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Egger <egger.m> |
Component: | Current packages | Assignee: | Henning Schild <henning> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | mgorny, np-hardass, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michael Egger
2019-05-09 17:27:46 UTC
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. |