Bug#367962: Please don't ship a /lib64 symlink in the package on amd64

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Aurelien Jarno <aurelien@aurel32.net> writes:

> Currently the (/usr)/lib64 -> /lib symlink is shipped in the libc6
> package. Goswin von Brederlow asked for this link to be created in the
> postinst instead, so that packages could install files in both
> (/usr)/lib and (/usr)/lib64 directories.
>
> I have concerns about that:
> - I don't really want to add something specific to amd64 in
> postinst. But ok, that's not an argument.
> - I am not sure that creating the link in postinst will work. Creating
> it in preinst looks safer to me.

yes.

> - If you can install files in (/usr)/lib64, the files will end up in
> (/usr)/lib. And dpkg won't know anything about them. dpkg -S and other
> tools won't work correctly.

Local admins are already allowed to convert directories into links,
e.g. to move parts ot the directory tree to another disk.

We had problems with that for the (/usr)/lib32 link used on amd64 and
for example dpkg-shlibs was afaik patched to deal with it
correctly. dpkg -S isn't but that could/should be fixed.

> - If you have two packages providing the same files in (/usr)/lib and
> (/usr)/lib64, then the files will be overwritten without warning. This
> is IMHO not acceptable.
>
> Could you please give me your opinion on that, so that I can take a
> decision?
>
> Thanks,
> Aurelien

MfG
        Goswin