| 1 |
On Sun, Sep 20, 2015 at 5:50 AM, Alexis Ballier <aballier@g.o> wrote: |
| 2 |
> |
| 3 |
> Yes, that's what gnome team is doing with gtk2 vs gtk3; however, I'm |
| 4 |
> not sure how much work it is. Only package I know of providing |
| 5 |
> different slots depending on what it's built upon is webkit-gtk. |
| 6 |
> |
| 7 |
> I can't imagine every library using {open,libre}ssl provide two slots, |
| 8 |
> two different libraries, two different pkg-config and the like files, |
| 9 |
> etc. And every package using a library that uses a library that uses a |
| 10 |
> library that uses {open,libre}ssl to have to chose what ssl library to |
| 11 |
> use. |
| 12 |
> |
| 13 |
|
| 14 |
I don't think the suggestion is to make it so that any package can be |
| 15 |
built against either, though individual maintainers can support this. |
| 16 |
|
| 17 |
I think the suggestion is to make it so that the libraries themselves |
| 18 |
can be installed side-by-side, so that packages can depend exclusively |
| 19 |
on one or the other and not effectively block each other. |
| 20 |
|
| 21 |
When other distros do it, that is essentially what they're doing. If |
| 22 |
apache on debian uses libssl, then it depends on it, and you can't |
| 23 |
install it using libressl (or if you can that is a separate pacakge). |
| 24 |
|
| 25 |
-- |
| 26 |
Rich |
Archives