Re: Enabling accessibility stack by default in Qt4/Qt5

2015-12-30 Thread Samuel Thibault
Hello, Sune Vuorela, on Wed 30 Dec 2015 17:02:01 +0100, wrote: > On Friday 11 December 2015 23:41:00 Samuel Thibault wrote: > > Lisandro Damián Nicanor Pérez Meyer, on Fri 11 Dec 2015 18:11:40 -0300, > wrote: > > > Ah, now I get it. Please go ahead. > > > > Good, now done! > > Konqueror seems

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-12-30 Thread Sune Vuorela
On Friday 11 December 2015 23:41:00 Samuel Thibault wrote: > Lisandro Damián Nicanor Pérez Meyer, on Fri 11 Dec 2015 18:11:40 -0300, wrote: > > Ah, now I get it. Please go ahead. > > Good, now done! Konqueror seems to crash for me now. Removing qt-at-spi fixes it. I don't know if there are

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-12-11 Thread Samuel Thibault
Lisandro Damián Nicanor Pérez Meyer, on Fri 11 Dec 2015 18:11:40 -0300, wrote: > Ah, now I get it. Please go ahead. Good, now done! Samuel -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-11-15 Thread Lisandro Damián Nicanor Pérez Meyer
On Saturday 14 November 2015 18:49:13 Samuel Thibault wrote: > Lisandro Damián Nicanor Pérez Meyer, on Sat 14 Nov 2015 14:28:53 -0300, wrote: [snip] > > As long as it depends on kde stuff I can only put it on Suggest (which I > > did) on libqtcore4. Any higher dependency would make normal

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-11-14 Thread Lisandro Damián Nicanor Pérez Meyer
On Sunday 18 October 2015 18:19:01 Sune Vuorela wrote: > On Sunday 18 October 2015 17:24:59 Samuel Thibault wrote: > > Hello, > > > > Could the qt-at-spi package be depended on by e.g. libqtcore4? > > Hi > > I guess one could put in a suggests somewhere, or maybe even a recommends, > but having

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-11-14 Thread Samuel Thibault
Lisandro Damián Nicanor Pérez Meyer, on Sat 14 Nov 2015 14:28:53 -0300, wrote: > On Sunday 18 October 2015 18:19:01 Sune Vuorela wrote: > > On Sunday 18 October 2015 17:24:59 Samuel Thibault wrote: > > > Hello, > > > > > > Could the qt-at-spi package be depended on by e.g. libqtcore4? > > > > Hi

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-11-14 Thread Samuel Thibault
Actually qt-at-spi needs libkdecore5 only for supporting translations, but AIUI there are currently no translations, and since qt-at-spi is not really to be maintained, I guess there won't be any. So I guess I'll just drop that support, thus releaving qt-at-spi from the libkdecore5 dependency.

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-11-14 Thread Samuel Thibault
Samuel Thibault, on Sat 14 Nov 2015 19:09:54 +0100, wrote: > So I guess I'll just drop that support, thus releaving qt-at-spi from > the libkdecore5 dependency. Done so in the 0.4.0-3 version. Samuel -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-10-22 Thread Lisandro Damián Nicanor Pérez Meyer
On Thursday 22 October 2015 22:43:50 Samuel Thibault wrote: > Samuel Thibault, le Sun 18 Oct 2015 18:30:05 +0200, a écrit : > > Sune Vuorela, le Sun 18 Oct 2015 18:19:01 +0200, a écrit : > > > On Sunday 18 October 2015 17:24:59 Samuel Thibault wrote: > > > > Could the qt-at-spi package be depended

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-10-18 Thread Samuel Thibault
Hello, Could the qt-at-spi package be depended on by e.g. libqtcore4? At the moment, we made orca explictly depend on qt-at-spi (through python-atspi), so that it is sure that it can read Qt4 applications. But that means that Qt libraries get pulled on gnome-only desktop too, which they don't

Re: Enabling accessibility stack by default in Qt4/Qt5

2015-10-18 Thread Sune Vuorela
On Sunday 18 October 2015 17:24:59 Samuel Thibault wrote: > Hello, > > Could the qt-at-spi package be depended on by e.g. libqtcore4? Hi I guess one could put in a suggests somewhere, or maybe even a recommends, but having it as a dependency would be making a dependency circle which I really