| 1 |
On Sat, 2014-02-22 at 15:59 -0600, Ryan Hill wrote: |
| 2 |
> On Sat, 22 Feb 2014 15:50:17 -0600 |
| 3 |
> Ryan Hill <dirtyepic@g.o> wrote: |
| 4 |
> |
| 5 |
> > On Sat, 22 Feb 2014 16:09:53 -0500 |
| 6 |
> > Alexandre Rostovtsev <tetromino@g.o> wrote: |
| 7 |
> > |
| 8 |
> > > On Sat, 2014-02-22 at 14:57 -0600, Ryan Hill wrote: |
| 9 |
> > > > wxGTK not only splits up libraries by version and toolkit, but also by |
| 10 |
> > > > charset and debug/release. If we had to use different SLOTs rather than |
| 11 |
> > > > USE flags we would need eight of them for 2.8 alone. And I don't know how |
| 12 |
> > > > we would name the ebuilds (-r100,-r200,... ugh). |
| 13 |
> > > |
| 14 |
> > > Remember, a single process cannot load both gtk2 and gtk3 - you *will* |
| 15 |
> > > get random crashes. If you think that dealing with interesting bug |
| 16 |
> > > reports - e.g. caused by application foo which was built against your |
| 17 |
> > > wxGTK[gtk3] and then crashed after enumerating its plugin directory |
| 18 |
> > > because of the presence of binary plugin bar which links to libbaz which |
| 19 |
> > > sometimes dlopens gtk2 at runtime when USE=wombat is enabled - is more |
| 20 |
> > > fun than doing a bit of work at the start and slotting wxGTK, then |
| 21 |
> > > please go ahead ;) |
| 22 |
> > |
| 23 |
> > Yeah and package built against wxGTK (gtk2) could dlopen gtk3 at runtime |
| 24 |
> > today. That's already the case. But what does that have to do with slotting? |
| 25 |
> |
| 26 |
> Oh. The libs are named explicitly: |
| 27 |
> |
| 28 |
> /usr/lib64/libwx_gtk2u_core-3.0.so |
| 29 |
> /usr/lib64/libwx_gtk3u_core-3.0.so |
| 30 |
> |
| 31 |
> You can't load the wrong one. |
| 32 |
|
| 33 |
Ah, I see. I was afraid you were proposing to use the same library name |
| 34 |
for wxGTK+gtk2 and wxGTK+gtk3. |
Archives