For re-locateable the symlink must be relative, it can not be absolute.
ln -sf ../../foo %{buildroot}%{_datadir}/bar
Thanks this works for the basic case.
However relative symlinks would work in cases when only symlink location can be changed but since rpm supports --relocate flag it can happen that also source file/directory can be relocated and then the relative path no longer helps.
Is there a non workaround solution for this or is this simply not supported by rpm out of the box?
However relative symlinks would work in cases when only symlink location can be changed but since rpm supports --relocate flag it can happen that also source file/directory can be relocated and then the relative path no longer helps.
Is there a non workaround solution for this or is this simply not supported by rpm out of the box?
For a workaround solution I guess that overriding existing symlink in %post section would work:
rm ${RPM_INSTALL_PREFIX1}/bar
ln -sf ${RPM_INSTALL_PREFIX0}/foo ${RPM_INSTALL_PREFIX1}/bar
This way rpm would keep track of symlink file and symlink would point to the right location.
Is there a better workaround solution - something that would hide the fact that the file was changed when querying rpm package for changes with -V?
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list
