Bug#913287: Is the SONAME the same for all the related libs?

To: 912925@bugs.debian.org
Cc: 913287@bugs.debian.org
Subject: Bug#913287: Is the SONAME the same for all the related libs?
From: Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com>
Date: Fri, 09 Nov 2018 08:36:17 -0300
Message-id: <[🔎] 3002435.vGzoLgUbgz@tonks>
Reply-to: Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com>, 913287@bugs.debian.org
References: <[🔎] 154172254072.927.5933470853297266999.reportbug@erdos.d-and-j.net>

Hi! Looking at the bug I do have a question: is the libGL.so.<n> SONAME the 
same on all the implementations?

I'm currently asking upstream why they are dlopening it instead of just 
linking to it, so knowing this detail will certainly help.

Thanks in advance!

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to:

References:
- Bug#913287: libqt5core5a: loads libGL.so instead of libGL.so.1, causing PyQt5 to crash on systems with NVIDIA libraries installed
  - From: Julian Gilbey <jdg@debian.org>

Prev by Date: Bug#913287: libqt5core5a: loads libGL.so instead of libGL.so.1, causing PyQt5 to crash on systems with NVIDIA libraries installed
Next by Date: Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
Previous by thread: Bug#913287: libqt5core5a: loads libGL.so instead of libGL.so.1, causing PyQt5 to crash on systems with NVIDIA libraries installed
Next by thread: Bug#913287: Bug#912925: Is the SONAME the same for all the related libs?
Index(es):
- Date
- Thread