Re: [gentoo-dev] Qt3 deprecation and removal policy
On 12/30/2009 12:14 PM, Ben de Groot wrote: 2010-01-21: * Qt team meeting: discuss actions to be taken regarding remaining pkgs that use qt:3 2010-02-21: * mask qt:3 and depending ebuilds, pending removal 30 days isn't a long time. How about filing bugs against anything that currently uses qt3 right away, so that maintainers have an extra three weeks to resolve these issues? Granted, one would hope they've been paying attention. As a random example, the current stable version of mythtv uses qt3, but I don't see any open bugs about that (that package is probably an easy fix as the newer versions use qt3support, and that version is already stable upstream). Usually the approach in these situations is to have a big tracker bug for qt3 removal and a million blocker bugs against individual packages. I'm not saying you can't move forward until everybody else gets their acts together, but tracking this in bugzilla probably isn't a bad move if it isn't too much work. Plus, you might decide that one or two of the blockers really are critical, and decide to work with those maintainers more closely or escalate the issue.
Re: [gentoo-dev] Qt3 deprecation and removal policy
On 12/31/2009 02:39 PM, Richard Freeman wrote: On 12/30/2009 12:14 PM, Ben de Groot wrote: 2010-01-21: * Qt team meeting: discuss actions to be taken regarding remaining pkgs that use qt:3 2010-02-21: * mask qt:3 and depending ebuilds, pending removal 30 days isn't a long time. How about filing bugs against anything that currently uses qt3 right away, so that maintainers have an extra three weeks to resolve these issues? Granted, one would hope they've been paying attention. As a random example, the current stable version of mythtv uses qt3, but I don't see any open bugs about that (that package is probably an easy fix as the newer versions use qt3support, and that version is already stable upstream). Stable MythTV has more issues than just Qt3, as the current stable doesn't compile anymore, http://bugs.gentoo.org/show_bug.cgi?id=280303 which is about to get masked tomorrow with kdelibs-3... Just saying...
Re: [gentoo-dev] Qt3 deprecation and removal policy
On 12/31/2009 07:51 AM, Samuli Suominen wrote: Stable MythTV has more issues than just Qt3, as the current stable doesn't compile anymore, http://bugs.gentoo.org/show_bug.cgi?id=280303 which is about to get masked tomorrow with kdelibs-3... Those of us who run it wouldn't mind seeing a STABLEREQ if cardoe thinks it is ready... :) I've been thinking about taking the plunge anyway. A news item about the utf-8 issues might not hurt though as doing the upgrade right involves backups/etc. The news item should be released BEFORE it goes stable. That is, unless the upgrade process has become seamless now.
Re: [gentoo-dev] Qt3 deprecation and removal policy
2009/12/31 Richard Freeman ri...@gentoo.org: 30 days isn't a long time. How about filing bugs against anything that currently uses qt3 right away, so that maintainers have an extra three weeks to resolve these issues? Granted, one would hope they've been paying attention. We've already announced that 5 months ago and asked for any issues to be brought to our attention. If things haven't improved by now, it is doubtful they will with a few months extra time. Our current timeline gives maintainers another seven weeks to resolve issues, before x11-libs/qt:3 will be package.masked. Usually the approach in these situations is to have a big tracker bug for qt3 removal and a million blocker bugs against individual packages. There is a tracker bug, I should have mentioned it in the original mail: https://bugs.gentoo.org/show_bug.cgi?id=283429 Please file bugs blocking the tracker for any package you think is important and doesn't have a Qt4 version or replacement yet. If there is a Qt4 version, but not yet stable, then stable requests should be filed, which also block the tracker. The Qt team will also go through the tree and file bugs for all remaining packages within the next couple of weeks. Plus, you might decide that one or two of the blockers really are critical, and decide to work with those maintainers more closely or escalate the issue. Sure. As I said in the original mail: We are dedicated to do anything we reasonably can to make sure that Qt4 versions or equivalents of the remaining Qt3 packages in the portage tree are available. I believe we can work things out in the next seven weeks, and otherwise we could reconsider the timeline. But we need short-term goals, otherwise it will take forever to get things done. Cheers, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) __
[gentoo-dev] Qt3 deprecation and removal policy
As announced 5 months ago[1], Gentoo's Qt team now officially deprecates usage of x11-libs/qt:3 and packages depending on this version of Qt. The only supported and maintained version of Qt, both by the upstream developers (Nokia) and the Gentoo Qt Project, is now only version 4 (specifically =4.5.3). As a result we have decided on a policy and timeline for the removal of qt:3 and ebuilds depending on it. We are dedicated to do anything we reasonably can to make sure that Qt4 versions or equivalents of the remaining Qt3 packages in the portage tree are available. The deprecated ebuilds for qt:3, and packages using it, will remain available in the community-maintained kde-sunset overlay. # Timeline # 2010-01-01: * mark qt:3 as deprecated with ewarn * mask qt3 useflag in profiles * add ewarn to qt3.eclass with link to removal policy * prepare news item about qt:3 deprecation and future removal 2010-01-21: * Qt team meeting: discuss actions to be taken regarding remaining pkgs that use qt:3 2010-02-21: * mask qt:3 and depending ebuilds, pending removal 2010-03-21: * remove qt:3 and depending ebuilds from the tree * remove masks * clean profiles from qt3 remnants * mark qt3.eclass as deprecated pending later removal # Policy for remaining ebuilds depending on qt:3 # * if Qt3 optional, remove this option * if Qt4 depending version stable, remove Qt3 depending versions * if Qt4 depending version in testing, mark stable, then remove older versions * if no Qt4 version in tree, get Qt4 version in testing by 2010-01-21 and stable by 2010-02-21 * if no Qt4 version exists, check for equivalent/replacement packages, and mask by 2010-02-21 Note: for packages that currently have no version marked stable, the references to stabling Qt4 versions obviously don't apply. 1: http://archives.gentoo.org/gentoo-dev-announce/msg_d851e05567d538b662f34de8dfdb7316.xml Cheers, -- Ben de Groot Gentoo Linux developer, Gentoo Qt Project lead __
Re: [gentoo-dev] Qt3 deprecation and removal policy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Em 30-12-2009 15:14, Ben de Groot escreveu: As announced 5 months ago[1], Gentoo's Qt team now officially deprecates usage of x11-libs/qt:3 and packages depending on this version of Qt. The only supported and maintained version of Qt, both by the upstream developers (Nokia) and the Gentoo Qt Project, is now only version 4 (specifically =4.5.3). As a result we have decided on a policy and timeline for the removal of qt:3 and ebuilds depending on it. We are dedicated to do anything we reasonably can to make sure that Qt4 versions or equivalents of the remaining Qt3 packages in the portage tree are available. The deprecated ebuilds for qt:3, and packages using it, will remain available in the community-maintained kde-sunset overlay. # Timeline # 2010-01-01: * mark qt:3 as deprecated with ewarn * mask qt3 useflag in profiles * add ewarn to qt3.eclass with link to removal policy * prepare news item about qt:3 deprecation and future removal 2010-01-21: * Qt team meeting: discuss actions to be taken regarding remaining pkgs that use qt:3 2010-02-21: * mask qt:3 and depending ebuilds, pending removal 2010-03-21: * remove qt:3 and depending ebuilds from the tree * remove masks * clean profiles from qt3 remnants * mark qt3.eclass as deprecated pending later removal # Policy for remaining ebuilds depending on qt:3 # * if Qt3 optional, remove this option * if Qt4 depending version stable, remove Qt3 depending versions * if Qt4 depending version in testing, mark stable, then remove older versions * if no Qt4 version in tree, get Qt4 version in testing by 2010-01-21 and stable by 2010-02-21 * if no Qt4 version exists, check for equivalent/replacement packages, and mask by 2010-02-21 Note: for packages that currently have no version marked stable, the references to stabling Qt4 versions obviously don't apply. 1: http://archives.gentoo.org/gentoo-dev-announce/msg_d851e05567d538b662f34de8dfdb7316.xml Cheers, A question: My systems don't use qt3 use flag since six months ago, but using qt3support USE FLAG. It's sane keep this flag set in make.conf? Thanks for now. p.s.: sorry if this is not the place to this question. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAks7ui8ACgkQ35zeJy7JhCiAxACgo/ebR4o+/gQa9/1+xjSTV0w8 kLoAoIueeG1xBlqwAR5XqBX1TrkqzRd5 =IquM -END PGP SIGNATURE-
Re: [gentoo-dev] Qt3 deprecation and removal policy
2009/12/30 Zhu Sha Zang zhushaz...@yahoo.com.br: Cheers, A question: My systems don't use qt3 use flag since six months ago, but using qt3support USE FLAG. It's sane keep this flag set in make.conf? If you use KDE or anything else that depends on the qt3support use flag, then it is a requirement. qt3support isn't Qt3, it is just an extra part of the Qt4 api for easing Qt3 - Qt4 porting. HTH Espen
Re: [gentoo-dev] Qt3 deprecation and removal policy
2009/12/30 Zhu Sha Zang zhushaz...@yahoo.com.br: A question: My systems don't use qt3 use flag since six months ago, but using qt3support USE FLAG. It's sane keep this flag set in make.conf? Absolutely. That useflag is also enabled by default in the desktop profile, because KDE4 depends on it. Qt3support is a Qt4 module and does not depend on qt:3. It is used to make it easier for developers to port Qt3 apps to Qt4. Cheers, -- Ben de Groot Gentoo Linux developer (qt, media, lxde, desktop-misc) __
