Ari Pollak wrote: > 64-bit RPMs that contain libraries generally install things into > /usr/lib64, which means that the /usr/lib64 directory is created by the > package when converted to a .deb with alien. However, libc6 owns the > /usr/lib64 symlink, and having a package install it would break things. > Therefore, I recommend that alien should convert /usr/lib64 to /usr/lib > when creating .deb packages.
The /usr/lib64 symlink only exists on amd64, right? Ie, on i386,
/lib/lib64 exists as a separate directory. There is also a /lib64 link on
amd64.
Which things exactly are broken by installing files from a deb into a
/usr/lib64 symlink? As long as the symlink is there before the package
is installed, dpkg should follow it:
A directory will never be replaced by a symbolic link to a
directory or vice versa; instead, the existing state (symlink or
not) will be left alone and `dpkg' will follow the symlink if
there is one.
--
see shy jo
signature.asc
Description: Digital signature
