[Slackbuilds-users] Build Environment Reminder

[Tonus]

Lumin Etherlight via SlackBuilds-users <slackbuilds-users at slackbuilds.org> writes:

>>> does that include package which explicitly state
>>> in the README that the package require the newer
>>> GLIBC?
>>>
>>> I maintain one such script (signal-desktop) and
>>> it would be a shame to see it removed from the
>>> repo.
>>>
>>>> Indeed.  Especially after somebody shared a
>>>> simple hack to get it to work under Slackware
>>>> 15.0.
>
> Willy Sudiarto Raharjo <willysr at slackbuilds.org> writes:
>
>> Unfortunately yes
>
>         Signal is  an important package,  so perhaps
>   we can make the SlackBuild patch the binary itself
>   and thus  it would work on  Slackware 15.0 without
>   user intervention.   I wrote  some instructions[1]
>   on my  website, and wrote a  script[2] to automate
>   the patching process.  The  patch forces Signal to
>   use a glibc install  in /opt using rpath.  Perhaps
>   we can  provide a simple  glibc-opt-bin SlackBuild
>   which would install glibc  from /testing into /opt
>   to support the installation of Signal (and perhaps
>   other packages that may  follow the same pattern).
>   I've been using  Signal on 15.0 for  more than two
>   months in this manner; it's stable and works well.
>
> [1]: https://lumin.etherlight.link/c/2C2606/mf3gC
> [2]: https://lumin.etherlight.link/s/2C2606/saNeW/slackware-signal-glibc-workaround.sh
>
>
> Best Regards,
> Lumin Etherlight

Hi all,

I agree that Signal is a must have. I've been using the workaround from
Lumin for weeks on at least 2 devices running stable 15.0.

This seems quite stable enough. I suggest the SlackBuild stays with a
%README% in the REQUIRES line of the .info file.

This could explain the needs of the testing glibc package and link to
the maintainer website for those that wouldn't go this path.

-- 
Regards,
Tonus.