Re: Removing Qt4 in Strech

2015-04-20 Thread Lisandro Damián Nicanor Pérez Meyer
On Monday 20 April 2015 18:41:26 Anton Gladky wrote:
 Hello,
 
 thanks for pushing this transition. What do you think, if I
 have a library, which is now built against qt4, should I just
 switch to qt5 or create lib-qt5-dev for the transition period?

The best thing to do is, if possible, provide a Qt4 and a Qt5 version.

If you do a direct change then all the apps that currently build depend on 
your library but can't switch now to Qt5 will have problems.

 The second question is the problem with armel and armhf
 qt5-builds. I think it will cause some problems [1] and would
 like to ask for a solution, which should be applied for all affected
 packages.
 
 [1] https://lists.debian.org/debian-qt-kde/2015/03/msg00233.html

Same as Sune already said: either get the code ported to another thing (GLU 
doesn not runs using opengl es) or disable those archs.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Removing Qt4 in Strech

2015-04-20 Thread Anton Gladky
Hello,

thanks for pushing this transition. What do you think, if I
have a library, which is now built against qt4, should I just
switch to qt5 or create lib-qt5-dev for the transition period?

The second question is the problem with armel and armhf
qt5-builds. I think it will cause some problems [1] and would
like to ask for a solution, which should be applied for all affected
packages.

[1] https://lists.debian.org/debian-qt-kde/2015/03/msg00233.html

Thanks

Anton


2015-04-19 19:53 GMT+02:00 Lisandro Damián Nicanor Pérez perezme...@gmail.com:
 On Thursday 16 April 2015 15:59:58 you wrote:
 Hi everyone! I have drafted a Qt4-removal announce in gobby, Teams→KDE→Qt4,
 right at the top.

 After some discussing with Dmitry on IRC we decided it would be better to
 start announcing Qt4's webkit removal and using that as propaganda for
 suggesting people to port their code to Qt5.

 According to dak that would mean ~96 source packages involved.

 I have updated the text in that regard, please give it a read :)

 Thanks, Lisandro.

 --
 Lisandro Damián Nicanor Pérez Meyer
 http://perezmeyer.com.ar/
 http://perezmeyer.blogspot.com/

 --
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Removing Qt4 in Strech

2015-04-16 Thread Andreas Cord-Landwehr
On Thursday 16 April 2015 15:58:58 Scott Kitterman wrote:
  I would also like some input from the KDE maintainers, specially (but not
  limited to) maxy on how KDE's porting efforts are being developed (for
  example, do you think we will have a usable KDE with Qt5 experience by the
  end of the year?) I haven't tried it myself yet so any input in this
  regard
  will be highly appreciated.
 
 Since Kubuntu is doing a largely Plasma5/Kf5/Qt5 release this month, I think
 we'll have a very good idea based on user feedback to Kubuntu about how
 usable the KDE/Qt5 experience is.  I haven't tried it either.

Hi, the porting progress of KDE Applications is currently working quite nicely 
IMO. An overview on what currently is already ported is e.g. here:

  http://developer.kde.org/~cfeck/portingstatus.html

Yet some important applications (e.g. the whole of PIM, Okular, Calligra...) 
have not seen any Qt5/KF5 based release yet. Trying to not make too bold 
statements, my gut feeling is that the KDE Applications release after 15.08 
(probably around X-Mas) should provide ports for most of the applications, 
making early 2016 sound a feasible date. If you add 4 more months for another 
Applications release cycle for safety, there should have been two Qt5/KF5 
based release cycles for most applications at spring 2016.

Talking about the Workspace, it is already quite usable IMO (whereas I am 
running master branches).

Cheers,
Andreas

-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk


Re: Removing Qt4 in Strech

2015-04-16 Thread Scott Kitterman
On Thursday, April 16, 2015 03:59:58 PM Lisandro Damián Nicanor Pérez Meyer 
wrote:
 Hi everyone! I have drafted a Qt4-removal announce in gobby, Teams→KDE→Qt4,
 right at the top.
 
 As many of you might know there are different feelings about this removal.
 On one hand we will not be having anything else but security-related bugs
 fixed in Qt4 from the next point release which should happen really soon
 until possibly 2017 (which is possibly one year after Strech's release). On
 the other hand the number of apps using Qt4 is just enormous.
 
 My suggestion to this is to simply try to get the removal done and see what
 happens during Strech's developing life cycle. Our experience with Qt3 was
 actually better that many think it was, having only 13 source packages using
 Qt3 when we asked for it's removal, and all of them where dead upstream
 (even if functional, like Twinkle).
 
 As usual I would like you to review the aforementioned removal announce.
 Feel free to edit it, that's why we have Gobby there.
 
 I would also like some input from the KDE maintainers, specially (but not
 limited to) maxy on how KDE's porting efforts are being developed (for
 example, do you think we will have a usable KDE with Qt5 experience by the
 end of the year?) I haven't tried it myself yet so any input in this regard
 will be highly appreciated.

Since Kubuntu is doing a largely Plasma5/Kf5/Qt5 release this month, I think 
we'll have a very good idea based on user feedback to Kubuntu about how usable 
the KDE/Qt5 experience is.  I haven't tried it either.

Scott K

-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Removing Qt4 in Strech

2015-04-16 Thread Lisandro Damián Nicanor Pérez Meyer
On Thursday 16 April 2015 18:43:52 Scott Kitterman wrote:
[snip]
 If you look at what paultag started regarding python3 migration (see dda), I
 think that's a good model for creating positive motivation to work on
 porting thing.

Right, although we don't have the porting team ;)

**Maybe** we should consider just announcing that Qt4 enters just-security-
bugs maintainance only and if someone wants to remove a dependency from Qt4's 
B-Ds we will do it as long as it just affects plugins and not API/ABI (which 
they shouldn't...)

-- 
OdyX They are plenty, a whole hurd of gnus.
* pinotree turns OdyX upside down
OdyX ˙snuƃ ɟo pɹnɥ ǝloɥʍ ɐ 'ʎʇuǝld ǝɹɐ ʎǝɥʇ
pinotree gh
OdyX (-: ˙ǝsɐǝןd 'dn ʞɔɐq ǝɯ uɹnʇ ǝsɐǝןd ʍou
* pinotree turns OdyX upside down again
OdyX Thank you.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Removing Qt4 in Strech

2015-04-16 Thread Scott Kitterman
On April 16, 2015 7:21:44 PM EDT, Lisandro Damián Nicanor Pérez Meyer 
perezme...@gmail.com wrote:
On Thursday 16 April 2015 18:43:52 Scott Kitterman wrote:
[snip]
 If you look at what paultag started regarding python3 migration (see
dda), I
 think that's a good model for creating positive motivation to work on
 porting thing.

Right, although we don't have the porting team ;)

**Maybe** we should consider just announcing that Qt4 enters
just-security-
bugs maintainance only and if someone wants to remove a dependency from
Qt4's 
B-Ds we will do it as long as it just affects plugins and not API/ABI
(which 
they shouldn't...)

He didn't have a porting team either until he called for volunteers today. 

Scott K


-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Removing Qt4 in Strech

2015-04-16 Thread Scott Kitterman
On April 16, 2015 6:29:17 PM EDT, Lisandro Damián Nicanor Pérez Meyer 
perezme...@gmail.com wrote:
On Thursday 16 April 2015 22:37:52 Andreas Cord-Landwehr wrote:
 On Thursday 16 April 2015 15:58:58 Scott Kitterman wrote:
[snip] 
 Hi, the porting progress of KDE Applications is currently working
quite
 nicely IMO. An overview on what currently is already ported is e.g.
here:
 
   http://developer.kde.org/~cfeck/portingstatus.html
 
 Yet some important applications (e.g. the whole of PIM, Okular,
Calligra...)
 have not seen any Qt5/KF5 based release yet. Trying to not make too
bold
 statements, my gut feeling is that the KDE Applications release after
15.08
 (probably around X-Mas) should provide ports for most of the
 applications, making early 2016 sound a feasible date. If you add 4
more
 months for another Applications release cycle for safety, there
should have
 been two Qt5/KF5 based release cycles for most applications at spring
2016.
 
 Talking about the Workspace, it is already quite usable IMO (whereas
I am
 running master branches).

Thanks you all for the feedback!

Having KDE at that guesstimate of june/july 2016 is actually quite
good, 
although it would have been better sooner for other non-KDE stuff to
follow. 
Anyways good news :)

Does any of you think of any way to gently push people to port their
stuff to 
Qt5 without calling it a removal at once? I do understand that we
might not 
be able to remove Qt4, but I *think* we should start pushing it
somehow. I'm 
open to other ideas :)

If you look at what paultag started regarding python3 migration (see dda), I 
think that's a good model for creating positive motivation to work on porting 
thing.

Scott K


-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Removing Qt4 in Strech

2015-04-16 Thread Scott Kitterman
On April 16, 2015 6:29:17 PM EDT, Lisandro Damián Nicanor Pérez Meyer 
perezme...@gmail.com wrote:
On Thursday 16 April 2015 22:37:52 Andreas Cord-Landwehr wrote:
 On Thursday 16 April 2015 15:58:58 Scott Kitterman wrote:
[snip] 
 Hi, the porting progress of KDE Applications is currently working
quite
 nicely IMO. An overview on what currently is already ported is e.g.
here:
 
   http://developer.kde.org/~cfeck/portingstatus.html
 
 Yet some important applications (e.g. the whole of PIM, Okular,
Calligra...)
 have not seen any Qt5/KF5 based release yet. Trying to not make too
bold
 statements, my gut feeling is that the KDE Applications release after
15.08
 (probably around X-Mas) should provide ports for most of the
 applications, making early 2016 sound a feasible date. If you add 4
more
 months for another Applications release cycle for safety, there
should have
 been two Qt5/KF5 based release cycles for most applications at spring
2016.
 
 Talking about the Workspace, it is already quite usable IMO (whereas
I am
 running master branches).

Thanks you all for the feedback!

Having KDE at that guesstimate of june/july 2016 is actually quite
good, 
although it would have been better sooner for other non-KDE stuff to
follow. 
Anyways good news :)

Does any of you think of any way to gently push people to port their
stuff to 
Qt5 without calling it a removal at once? I do understand that we
might not 
be able to remove Qt4, but I *think* we should start pushing it
somehow. I'm 
open to other ideas :)

If you look at what paultag started regarding python3 migration (see dda), I 
think that's a good model for creating positive motivation to work on porting 
thing.

Scott K


-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Removing Qt4 in Strech

2015-04-16 Thread Lisandro Damián Nicanor Pérez Meyer
On Thursday 16 April 2015 22:37:52 Andreas Cord-Landwehr wrote:
 On Thursday 16 April 2015 15:58:58 Scott Kitterman wrote:
[snip] 
 Hi, the porting progress of KDE Applications is currently working quite
 nicely IMO. An overview on what currently is already ported is e.g. here:
 
   http://developer.kde.org/~cfeck/portingstatus.html
 
 Yet some important applications (e.g. the whole of PIM, Okular, Calligra...)
 have not seen any Qt5/KF5 based release yet. Trying to not make too bold
 statements, my gut feeling is that the KDE Applications release after 15.08
 (probably around X-Mas) should provide ports for most of the
 applications, making early 2016 sound a feasible date. If you add 4 more
 months for another Applications release cycle for safety, there should have
 been two Qt5/KF5 based release cycles for most applications at spring 2016.
 
 Talking about the Workspace, it is already quite usable IMO (whereas I am
 running master branches).

Thanks you all for the feedback!

Having KDE at that guesstimate of june/july 2016 is actually quite good, 
although it would have been better sooner for other non-KDE stuff to follow. 
Anyways good news :)

Does any of you think of any way to gently push people to port their stuff to 
Qt5 without calling it a removal at once? I do understand that we might not 
be able to remove Qt4, but I *think* we should start pushing it somehow. I'm 
open to other ideas :)

-- 
Antiguo proverbio de El Machi: Dado el apropiado grado de profundidad, la
ineptitud es indistinguible del sabotaje

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk