Re: /usr/lib64 or /usr/lib

[Goswin von Brederlow <goswin-v-b@web.de>]

Russ Allbery <rra@debian.org> writes:

> Sven Joachim <svenjoac@gmx.de> writes:
>
>> Er no, this is not how dpkg behaves.  It never converts symlinks to
>> directories or vice versa, so the actual outcome is¹ that your file gets
>> actually installed into /usr/lib through the symlink.  This means that
>> if another package starts shipping a file with the same name in
>> /usr/lib, dpkg will not notice the file conflict which is bad.
>
>> It's much worse if you ship files in /lib64, because if your package is
>> installed into a chroot and unpacked by the host dpkg with the --root=â?¦
>> option, the files end up in the host system².
>
> So we should absolutely forbid this in Policy instead of just removing the
> requirement.  I'll open a bug against debian-policy for this.

Forbid what? Absolut symlinks? Or packages shipping files in directories
that are symlinks in other packages?

The later is already a RC bug.

MfG
        Goswin