Re: Bug#1091995: tech-ctte: clarify authority of aliasing symbolic links
Helmut Grohne wrote:
> As far as I understand it, we may pick any three:
> * Allow systemd to manage /lib64 as it does.
> * /usr-move
> * Multiarch
> * Multilib
By "/usr-move", do you mean the overall /usr migration, or do you mean
the idea of linking /lib64 to /usr/lib64 unconditionally (e.g. in
base-files)? The latter seems like a viable solution, and a *useful* one
for multiarch. If someone is on arm64 (without /lib64), and they want to
have amd64 libraries installed, *something* needs to be responsible for
installing a /lib64 symlink to /usr/lib64, and base-files seems like the
obvious candidate to do so. That would avoid having to have any special
logic in packages that need /lib64. The only cost would be having an
"unnecessary" symlink on targets like arm64 (which stops being
unnecessary as soon as the system installs multiarch packages from a
target that needs /lib64).
Reply to: