| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 30/09/15 07:42 AM, hasufell wrote: |
| 5 |
> * libressl has to conflict with openssl |
| 6 |
|
| 7 |
Right now libressl exports many of the same symbols as openssl |
| 8 |
right? What if it didn't -- that is, we forced a symver map with a |
| 9 |
libressl prefix on all symbols? That would ensure anything built |
| 10 |
against libressl would not b0rk if openssl was loaded, or more |
| 11 |
specifically, if something else was loaded that was built against |
| 12 |
and links to openssl. |
| 13 |
|
| 14 |
This wouldn't need any rdep patching at all, and would ensure symbol |
| 15 |
collisions between the two projects would not occur. It doesn't |
| 16 |
explicitly enable side-by-side installation but it would help ensure |
| 17 |
things built for one project wouldn't use symbols from the other's |
| 18 |
lib expecting compatibility and randomly fail. |
| 19 |
|
| 20 |
...or am I mis-understanding the major issue with the |
| 21 |
libressl/openssl conflict? |
| 22 |
|
| 23 |
|
| 24 |
-----BEGIN PGP SIGNATURE----- |
| 25 |
Version: GnuPG v2 |
| 26 |
|
| 27 |
iF4EAREIAAYFAlYMC3EACgkQAJxUfCtlWe34nwD+N+4s1ZFVLS8CGokYOEa64U6o |
| 28 |
EINP0tsAe2EyA/cpy6oBANoIyxf7bfPStLPofV1ZW7/7+z3DsmtSqYztsU6dptmz |
| 29 |
=oAIp |
| 30 |
-----END PGP SIGNATURE----- |
Archives