I have gone ahead and simply used ${LN}, after checking with Allan Jude.
I understand that there are definitely use cases for using ${RLN}, but this
feels to me like one of the corner cases where when the handbook says “strongly
recommended“ and not “must” implies having a really good reason sort of
overrides that.
In this case, it’s the fact that some (bug | undocumented security feature) is
in the Linux emulator, that specifically breaks with overloaded relative links.
And on a given machine, the target will always be into wherever ${LINUXBASE}
is.
Sent from my iPhone
> On Oct 7, 2025, at 20:46, Tatsuki Makino <[email protected]> wrote:
>
> Hello.
>
>> On 2025/10/06 9:09, Dan Mahoney (ports) wrote:
>> do-install:
>> cd ${WRKSRC}; ${CP} -pR * ${STAGEDIR}${PREFIX}
>> ${RLN} ${LINUXBASE}/lib64/libssl.so.3
>> ${STAGEDIR}${PREFIX}/opt/dell/srvadmin/lib64/openmanage/private/libssl.so
>
> This might mean that it is a good idea to place a dummy file under
> ${STAGEDIR}${PREFIX} first and then execute the ${RLN} to create the symlink
> to ${STAGEDIR}${PREFIX}/lib64/libssl.so.3.
>
> Regards.
