A couple of side effects for distribution packages since megadrivers and using hardlinks: 1) hardlinks get copied as different files on packages, each one occupying the same size, unless a trick is used to keep the hardlinks. In Debian and Ubuntu the workaround is applied correctly 2) only one debug file is provided, ignoring the hardlinked files, see Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755921 Workaround is simple (manually create symlinks), but not used currently. No idea if there is a better approach (symlinks rather than hardlinks?), just writing here to document it, otherwise this can be closed.
(In reply to comment #0) > A couple of side effects for distribution packages since megadrivers and > using hardlinks: > 1) hardlinks get copied as different files on packages, each one occupying > the same size, unless a trick is used to keep the hardlinks. In Debian and > Ubuntu the workaround is applied correctly Not sure why you'll call it a "trick" but if you insist. > 2) only one debug file is provided, ignoring the hardlinked files, see > Debian bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755921 > Workaround is simple (manually create symlinks), but not used currently. > Getting a debug package for Archlinux and Fedora seems to work like a charm. All the files are where they should be, and the package contains only one copy of the debug symbols while the rest of the files hardlink to it. This might be a nice way/time for Debian's dh_strip to "catch-up" :P > No idea if there is a better approach (symlinks rather than hardlinks?), > just writing here to document it, otherwise this can be closed. > Why hardlinks: * The only way to get old libGL with new megadriver dri modules working. * There was another case but I don't quite recall the details. * One less file to worry about (and to get wrong) :) Kind request - please fix/enhance dh_strip :)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.