Re: Wrappers don't transform @file syntax

[PHO <pho%cielonegro.org@localhost>]

On 2020-01-17 19:36, Jonathan Perkin wrote:
> * On 2020-01-17 at 10:02 GMT, Patrick Welche wrote:
> 
>> On Wed, Jan 15, 2020 at 03:42:17PM +0100, Joerg Sonnenberger wrote:
>>> Please do not use $ORIGIN. It's a constant source of issues.
>>
>> My view is that the indescriminate removal of $ORIGIN at several stages
>> of cwrappers operation is a constant source of issues.
> 
> It's very important to consider the context of when issues will arise
> when debating $ORIGIN.
> 
> We've chosen to ensure that the issues are exposed at build time, in a
> controlled environment, where a solution can be found that may take a
> little longer, but will ensure that once fixed we can have confidence
> that the binaries will function correctly and in an orderly manner
> without being affected by changes to the environment.
> 
> Allowing $ORIGIN moves the exposure to run time.  In production.  When
> something is going wrong that you're struggling to figure out, the
> site is down, and customers are screaming at you to get things up and
> running again.
> 
> I know which I'd prefer.
> 

In case I need to make it clear, I am not willing to eliminate the use
of $ORIGIN in lang/ghc*. It's the upstream that chose to use it after
all, and they are doing so for reasons. Patching GHC to prevent it means
significant rewrite of its AMAZINGLY complicated build system, and even
if I managed to do that, the patch has basically no chance of being
merged to the upstream because it would break their use case.