[Slackbuilds-users] Build Environment Reminder

[Christoph Willing]

I've never use signal before so can't check history but QR link & sync 
seem to work OK here.

I'm not sure if it meets all other admins requirements but if put to a 
vote my vote would be "aye" if only because it's such a cute solution.

chris


On 13/8/26 21:06, Yiannis wrote:
> Just to be clear, this is not the same as installing the testing glibc.
>
> Nothing on the system changes. System glibc stays 2.33. No upgradepkg 
> of a core package, no ld.so.conf, no ldconfig.
>
> What the script does:
>
> - unpacks the snap into /opt/Signal/signal-desktop
> - unpacks aaa_glibc-solibs-2.42 into the same prefix, as a build 
> source like any tarball
> - patchelf on the Electron binary so its PT_INTERP and DT_RPATH point 
> there
>
> So those .so files are reachable by exactly one binary. Nothing else 
> on the machine can see them, and removepkg takes them all with it.
>
> Checked: /proc/PID/maps across all 7 Signal processes shows only the 
> bundled libc, never the host 2.33. QR link, full history sync, send 
> and receive all work. sbopkglint passes.
>
> Attached if anyone wants to look.
>
> IF admins and the maintainer agree with that then a desktop entry and 
> an icon needed, now run only from the terminal.
>
> Thank you.
>
> Στις Πέμ 13 Αυγ 2026 στις 12:05 μ.μ., ο/η Yiannis <rizitis at gmail.com> 
> έγραψε:
>
>     Please give me some time, I have an idea and it looks that works!
>     When I finish and be sure I will upload it here and IF maintainer
>     and SBo admins agree you can adopt it.
>
>
>     Στις Πέμ 13 Αυγ 2026 στις 7:13 π.μ., ο/η Willy Sudiarto Raharjo
>     <willysr at slackbuilds.org> έγραψε:
>
>         >       Signal blocks old versions of their software
>         >  from connecting  to the network.  I  had to figure
>         >  out  the binary  patching thing  because the  last
>         >  15.0  glibc-compatible version  I had  was finally
>         >  blocked from connecting to the Signal network.
>         >
>         >        If patching the rpath to use an isolated new
>         >  glibc-opt without migrating the whole OS is not an
>         >  acceptable solution for  the SlackBuilds.org repo,
>         >  then removing the Signal  SlackBuild is the option
>         >  that makes sense, in my opinion.  People who still
>         >  want to use Signal will  have to install it from a
>         >  different 3rd party.  If that happens, I might end
>         >  up packaging the patched  version myself, and then
>         >  redistribute it on my site for others to use.
>
>
>         What about the AppImage format?
>         will that work?
>         i assume it's all contained in a single package, so no link to
>         system-based GLIBC
>
>
>         --
>         Willy Sudiarto Raharjo
>         _______________________________________________
>         SlackBuilds-users mailing list
>         SlackBuilds-users at slackbuilds.org
>         https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>         Archives -
>         https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>         FAQ - https://slackbuilds.org/faq/
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260813/5686110a/attachment-0001.htm>