You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using cairo2-pango (in combination with cairo2, but that's it). Currently, cairo2-pango brings all of lablgtk as a dependency, which is a bit unfortunate. If I understand correctly, this is because because lablgtk binds bits of pango itself, and indeed, I'm using some functions from lablgtk's Pango module.
How hard would it be to make the dependencies of cairo2-pango more lightweight, possibly by separating the pango bindings from the rest of lablgtk?
The text was updated successfully, but these errors were encountered:
I've seen that there's also some coordination effort happening between cairo2 and lablgtk for lablgtk3, but I don't know whether that would be related to this issue?
The pango module needs to be split from the lablgtk package to enable a finer grained dependency. Please open an issue explaining your aim on the lablgtk tracker and let's see what happens from there.
I'm using cairo2-pango (in combination with cairo2, but that's it). Currently, cairo2-pango brings all of lablgtk as a dependency, which is a bit unfortunate. If I understand correctly, this is because because lablgtk binds bits of pango itself, and indeed, I'm using some functions from lablgtk's Pango module.
How hard would it be to make the dependencies of cairo2-pango more lightweight, possibly by separating the pango bindings from the rest of lablgtk?
The text was updated successfully, but these errors were encountered: