Find and fix broken symlinks

[jpecar]

While playing with packing up EESSI into a container I found out that compat layer includes some dangling symlinks and some files, unreadable to unprivileged user. May I suggest to add something like find $EESSI_PREFIX -xtype l to some test suite to find such files and fix them before rolling out new version?

[boegel]

Those symbolic links will indeed be broken on some operating systems (say CentOS), but not in others (say Ubuntu).

They were put in place a while ago for good reasons, see for example #89 and #105

[jpecar]

Hosts and localtime are not problematic, what I'm hitting is etc/runlevels/sysinit/kmod-static-nodes, lib64/libnss_centrifydc.so.2, lib64/libnss_ldap.so.2 and a couple of unreadable files and folders, like etc/ssl/private, var/log/sandbox. Not sure what we want to do with these ...

Also there are a couple dangling symlinks in the software tree (like WRF) but I guess we should handle those separately.