<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 11/8/26 07:38, Greg Tourte wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAK09-v=o9q5_HHRr9eZm9LD6qihSoU8TA=P9QaYz97hoAH7A=g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:monospace,monospace;font-size:x-small">Willy,</div>
<div class="gmail_default"
style="font-family:monospace,monospace;font-size:x-small"><br>
</div>
<div class="gmail_default"
style="font-family:monospace,monospace;font-size:x-small">does
that include package which explicitly state in the README that
the package require the newer GLIBC?</div>
<div class="gmail_default"
style="font-family:monospace,monospace;font-size:x-small"><br>
</div>
<div class="gmail_default"
style="font-family:monospace,monospace;font-size:x-small">I
maintain one such script (signal-desktop) and it would be a
shame to see it removed from the repo.</div>
</div>
</blockquote>
<br>
<font face="monospace">I suggest reverting the VERSION to the last
one that worked without newer GLIBC - I guess 8.1.0 (as for
signal-desktop-legacy, which could then be removed). The README
could then be expanded to mention that later versions would
require the newer GLIBC but could still be "built" by setting the
VERSION appropriately in the environment e.g.<br>
VERSION=8.21.0 bash signal-desktop.SlackBuild<br>
<br>
Whenever a new version is released, the README could be updated
acccordingly rather than updating signal-desktop.{info,SlackBuild}
as would normally be the case<br>
<br>
This way a user would always be able to run the latest version
provided they install the newer GLIBC (which they already need to
do at the moment anyway).<br>
<br>
chris<br>
<br>
</font>
</body>
</html>