On 02/16/2018 10:53 PM, Richard W.M. Jones wrote:
There are some %post scripts which still use this, notably ca-certificates, so that's now broken.
What do you propose instead? Revert the removal, exposing SELinux and other issues because some tools do not deal properly with hardlinks? Or reintroduce the copy, consuming storage in container images which no one needs?
But more to the point what do you do if you are in a situation where you need to make a symlink to save some core shared library on the currently running system?
That's an argument for packaging busybox-static, sash, or maybe work on a statically linked tool which runs an unpacked initramfs in a chroot.
Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
