Re: $ORIGIN in RPATH suppression

[Greg Troxel <gdt%lexort.com@localhost>]

pin <voidpin%protonmail.com@localhost> writes:

> On Thursday, January 2nd, 2025 at 5:57 PM, Greg Troxel <gdt%lexort.com@localhost> wrote:
>
>> pin voidpin%protonmail.com@localhost writes:
>>
>> So separately from how the world ought to be (that rust upstream
>> inexplicably doesn't value), I mean that anyone checking out pkgsrc
>> should be able to do anything he@ can do, so "he@ carries patches that
>> aren't committed" isn't a reasonable approach.
>
> Fair enough, thanks for explaining, that didn't really came through in the initial short version.
>
> But, how do we go from here?
> Right now we have 1.81, although I'm confident that 1.82 could in principle be merged.
> What to do with 1.83? And in 7 days 1.84?

I agree that the royal we need to find a path.

It could be as ugly as a package that installs scripts that does the
cross builds and patches up the rpaths, so the builds aren't done under
wrappers, but still the recipe is checked in.