[Development] Qt 5 beta 2 packages for testing
Hi, New packages for Windows (only 32-bit), Linux and Mac are available for testing at: http://releases.qt-project.org/digia/5.0.0_beta2/backups/2012-11-12-341/ There are no known blockers in these packages, so they should be considered a candidate for Qt 5 beta 2 release, that we hope to release tomorrow (Note that win 64 is not planned to be released for Qt 5 beta 2). If you find an issue in these packages, that you believe to be a blocker. Please post a message about this on releas...@qt-project.org (in addition to creating the bugreport). Relevant information (that was mentioned previously): - The list of known issues and workarounds: http://qt-project.org/wiki/Qt500beta2KnownIssues. If you find anything that is not already there, please feel free to update the wiki with your findings. - Qt bug reports (in https://bugreports.qt-project.org/) should be reported with Affects Version/sRequired = '5.0.0 Beta 2'. - Qt Creator bug reports (in https://bugreports.qt-project.org/) should be reported with Affects Version/sRequired = 'Qt Creator 2.6.0-rc' Labels = 'creator_qt5'. Br, Sinan ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QT 5 beta 2 snapshot : no debug dll for qml
Hi, I have tryed last beta 2 snapshot for windows and there is always no debug version of qml 2 import ... so It's impossible to debug an application that use qml. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5 Beta - undefined reference to QWidget
Hi, I'm testing Qt 5 Beta with a simple Qt Widget Project on Linux. Mainly it's the one you get when creating a new project without any forms. In the .pro file I added widgets, qml and quick to the QT-variable. When compiling the project I get the following errors: moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xc4): undefined reference to `QWidget::styleChange(QStyle)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xc8): undefined reference to `QWidget::enabledChange(bool)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xcc): undefined reference to `QWidget::paletteChange(QPalette const)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xd0): undefined reference to `QWidget::fontChange(QFont const)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xd4): undefined reference to `QWidget::windowActivationChange(bool)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xd8): undefined reference to `QWidget::languageChange()' Any idea on how to fix it? Best regards Fabian___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5 Beta - qtwebkit build error
Hi, I am trying to build the new Qt 5 beta 1 on Fedora 16. My problem is that qtwebkit is throwing following error: make[1]: Entering directory `/home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1' test -d qtwebkit || mkdir qtwebkit cd qtwebkit export WEBKITOUTPUTDIR=/home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtwebkit/WebKitBuild perl /home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtwebkit/Tools/Scripts/build-webkit --qt --qmake=/home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtbase/bin/qmake --install-libs=/usr/local/qt/desktop-qt5.0.0-beta/lib --qmakearg=CONFIG+=production_build --release --no-webkit2 Can't locate version.pm in @INC (@INC contains: /home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtwebkit/Tools/Scripts /usr/local/lib/perl5 /usr/local/share/perl5 /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5 /usr/share/perl5 .) at /home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtwebkit/Tools/Scripts/webkitdirs.pm line 32. BEGIN failed--compilation aborted at /home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtwebkit/Tools/Scripts/webkitdirs.pm line 32. Compilation failed in require at /home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtwebkit/Tools/Scripts/build-webkit line 41. BEGIN failed--compilation aborted at /home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1/qtwebkit/Tools/Scripts/build-webkit line 41. make[1]: *** [module-qtwebkit] Error 2 make[1]: Leaving directory `/home/local/CW01/uidu5861/qt/qt-everywhere-opensource-src-5.0.0-beta1' make: *** [sub-qtwebkit-pri-make_first] Error 2 Looks like the problem is coming from wekitdirs.rpm. I tried also to build webkit with following command, but the problem remains the same: perl Tools/Scripts/build-webkit --qt --qmake=../qtbase/bin/qmake --install-libs=/usr/local/qt/desktop-qt5.0.0-beta --release --makeargs=$MAKEFLAGS The interesting thing is that the configure argument -nomake webkit doesn't affect this problem. Is there a workaround/patch for this issue? Regards, Dietrich___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 Beta - undefined reference to QWidget
On segunda-feira, 10 de setembro de 2012 10.55.21, Fabian.Gruber@conti- engineering.com wrote: Hi, I'm testing Qt 5 Beta with a simple Qt Widget Project on Linux. Mainly it's the one you get when creating a new project without any forms. In the .pro file I added widgets, qml and quick to the QT-variable. When compiling the project I get the following errors: moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xc4): undefined reference to `QWidget::styleChange(QStyle)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xc8): undefined reference to `QWidget::enabledChange(bool)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xcc): undefined reference to `QWidget::paletteChange(QPalette const)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xd0): undefined reference to `QWidget::fontChange(QFont const)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xd4): undefined reference to `QWidget::windowActivationChange(bool)' moc_mainwindow.o:(.data.rel.ro._ZTV10MainWindow[vtable for MainWindow]+0xd8): undefined reference to `QWidget::languageChange()' Any idea on how to fix it? In your .pro file, make sure you have: QT += widget -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 Beta - qtwebkit build error
On segunda-feira, 10 de setembro de 2012 11.04.29, Dietrich.Gossen@conti- engineering.com wrote: Can't locate version.pm in @INC Please install Perl::version. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
Hello all, Le 30/08/2012 14:33, Yves Bailly a écrit : Le 30/08/2012 13:23, lars.kn...@nokia.com a écrit : the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta Trying to compile on Windows 7 64bits using MSVC 2010 (32bits compiler). After having read the provided README. NMAKE : fatal error U1077: 'C:\vs10\VC\BIN\cl.EXE' : return code '0x2' Stop. *** qtbase/configure exited with non-zero status. No more idea about this compiling issue? it's quite frustrating... -- /- Yves Bailly - Software developper -\ \- Sescoi RD - http://www.sescoi.fr -/ The possible is done. The impossible is being done. For miracles, thanks to allow a little delay. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On 31.08.2012 09:00, Yves Bailly wrote: Hello all, Le 30/08/2012 14:33, Yves Bailly a écrit : Le 30/08/2012 13:23, lars.kn...@nokia.com a écrit : the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta Trying to compile on Windows 7 64bits using MSVC 2010 (32bits compiler). After having read the provided README. NMAKE : fatal error U1077: 'C:\vs10\VC\BIN\cl.EXE' : return code '0x2' Stop. *** qtbase/configure exited with non-zero status. No more idea about this compiling issue? it's quite frustrating... Start from scratch. Be sure your source directory is not polluted with a previous build, therefore build out of source so you could simply throw away a failed build deleting the complete build folder. When it fails post the complete output, also the content of your PATH variable: 'set' prints all environment variables. Peter ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
Le 31/08/2012 09:05, Thiago Macieira a écrit : On sexta-feira, 31 de agosto de 2012 09.00.40, Yves Bailly wrote: NMAKE : fatal error U1077: 'C:\vs10\VC\BIN\cl.EXE' : return code '0x2' Stop. *** qtbase/configure exited with non-zero status. No more idea about this compiling issue? it's quite frustrating... Please note each try is done from a clean, just-unpacked archive (hard learned lesson after 15 years of experience building Qt releases...) It looks like perl wasn't found, so the forwarding headers weren't created. Well, Perl (ActiveState) should be found, at least it's in PATH: D:\qt\qt5-5.0.0-win32-msvc2010perl -v This is perl 5, version 14, subversion 2 (v5.14.2) built for MSWin32-x64-multi-thread (with 1 registered patch, see perl -V for more detail) Copyright 1987-2011, Larry Wall Binary build 1402 [295342] provided by ActiveState http://www.ActiveState.com Built Oct 7 2011 15:19:36 Ensure that perl is in PATH and re-run configure. If that still fails, run syncqt manually and let us know if that produces errors: perl bin/syncqt ...and now it works... I really don't know what happened, maybe an unlikely error while unpacking... configure worked, compiling right now. Sorry for the noise. Last word at last, despite the troubles I encountered (which may well be my fault): a great thank and congratulation to all those who made that release even possible, despite all the troubles and non-technical mess. Regards, -- /- Yves Bailly - Software developper -\ \- Sescoi RD - http://www.sescoi.fr -/ The possible is done. The impossible is being done. For miracles, thanks to allow a little delay. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On my suggestion, we dropped .tar.bz2. We're keeping .tar.gz to ensure maximum compatibility and .tar.xz because it's the smaller of the three. Was this decision publicly discussed on the mailing list (development, release, or both)? Perhaps, it is just me, but I have just skimmed through the release mailing list, but I have not caught this discussion. Laszlo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5 Beta - Qt Location 5.0
Hi, I installed Qt 5 Beta, now I want to work with Qt 5 Location. I'm using Qt Location with QML. import QtLocation 5.0 At the projectfile I added QT += location When I compile the project I don't get an error, because qml will be interpreted by runtime. But Qt Location does not work and i get the message: Module 'QtLocation' does not contain a module identifier directive - it cannot be protected from external registrations. Can anyone help me? Thank You.___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On sexta-feira, 31 de agosto de 2012 12.05.00, Laszlo Papp wrote: On my suggestion, we dropped .tar.bz2. We're keeping .tar.gz to ensure maximum compatibility and .tar.xz because it's the smaller of the three. Was this decision publicly discussed on the mailing list (development, release, or both)? Perhaps, it is just me, but I have just skimmed through the release mailing list, but I have not caught this discussion. On the #qt-release channel, then reviewed through Gerrit. https://codereview.qt-project.org/33837 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On 31.08.2012 13:31, Thiago Macieira wrote: On sexta-feira, 31 de agosto de 2012 12.05.00, Laszlo Papp wrote: On my suggestion, we dropped .tar.bz2. We're keeping .tar.gz to ensure maximum compatibility and .tar.xz because it's the smaller of the three. Was this decision publicly discussed on the mailing list (development, release, or both)? Perhaps, it is just me, but I have just skimmed through the release mailing list, but I have not caught this discussion. On the #qt-release channel, then reviewed through Gerrit. https://codereview.qt-project.org/33837 This is a little bit behind closed doors. Similar to the decision releasing beta without any note on the list. Peter ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On sexta-feira, 31 de agosto de 2012 13.40.38, Peter Kümmel wrote: On the #qt-release channel, then reviewed through Gerrit. https://codereview.qt-project.org/33837 This is a little bit behind closed doors. Similar to the decision releasing beta without any note on the list. It wasn't closed-doors. The commit was public. If you wanted to find out about it, you could have set up a Gerrit notification on the qtrepotools repository. The #qt-labs channel had a link to #qt-releases on its topic, inviting everyone to participate in the process. We can't very well announce every single change we're making on the mailing list. I only post when it's large, relevant for others, or when I really need input from others. Finally, this *was* a subjective choice: mine. I want to drive adoption of newer, better technology. LZMA is a great improvement over the compression technologies used so far and the xz format is getting interesting adoption. Many thanks to Julian Seward for bzip2 (among other projects he's contributed to), but xz is producing smaller packages nowadays. So, I'd say that our position is: stop complaining and upgrade. If you can't upgrade, there's .gz and you'll pay the penalty by increased disk space in your system. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On 31.08.2012 13:54, Thiago Macieira wrote: On sexta-feira, 31 de agosto de 2012 13.40.38, Peter Kümmel wrote: On the #qt-release channel, then reviewed through Gerrit. https://codereview.qt-project.org/33837 This is a little bit behind closed doors. Similar to the decision releasing beta without any note on the list. It wasn't closed-doors. The commit was public. If you wanted to find out about it, you could have set up a Gerrit notification on the qtrepotools repository. The #qt-labs channel had a link to #qt-releases on its topic, inviting everyone to participate in the process. We can't very well announce every single change we're making on the mailing list. I only post when it's large, relevant for others, or when I really need input from others. Finally, this *was* a subjective choice: mine. I want to drive adoption of newer, better technology. LZMA is a great improvement over the compression technologies used so far and the xz format is getting interesting adoption. Many thanks to Julian Seward for bzip2 (among other projects he's contributed to), but xz is producing smaller packages nowadays. So, I'd say that our position is: stop complaining and upgrade. If you can't upgrade, there's .gz and you'll pay the penalty by increased disk space in your system. I also prefer LZMA, this was just a comment about the process. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
So, I'd say that our position is: stop complaining and upgrade. If you can't upgrade, there's .gz and you'll pay the penalty by increased disk space in your system. First: no, that is not true. We will store the upstream tarball as bz2 on the Community OBS anyway due to the debian tools and technology on the community OBS what we have. Second: premature disk space optimization is not a problem for us, but the RAM usage is. The small size has a price. Thirdly: The conversion is very slow in scratchbox which the developers use locally and also on the build server. Fourthly: I have not said xz would not be good, if it was as common as bz2 which is not right now among certain people. Moreover, we have an open process for discussing development related issues on the development mailing list, and I would personally propose to have that for the release process as well. I am sorry, but I cannot (and do not wish) hang around IRC all the day along, and filter for gerrit is suboptimal for community discussions. You could say the same for the development related topic, you just need to follow Gerrit, but this is not how the community decided back then about that process. I like the community decision about this very much, and I would like to see the same happening about the releases. Laszlo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On sexta-feira, 31 de agosto de 2012 13.08.39, Laszlo Papp wrote: So, I'd say that our position is: stop complaining and upgrade. If you can't upgrade, there's .gz and you'll pay the penalty by increased disk space in your system. First: no, that is not true. We will store the upstream tarball as bz2 on the Community OBS anyway due to the debian tools and technology on the community OBS what we have. It's your choice to unpack and repack. Second: premature disk space optimization is not a problem for us, but the RAM usage is. The small size has a price. gzip has a smaller memory footprint than them all. Thirdly: The conversion is very slow in scratchbox which the developers use locally and also on the build server. Don't convert then. Use the .gz file. Moreover, we have an open process for discussing development related issues on the development mailing list, and I would personally propose to have that for the release process as well. We have that. But this was a minor issue. I certainly did not expect it to become this major a sore point. I am sorry, but I cannot (and do not wish) hang around IRC all the day along, and filter for gerrit is suboptimal for community discussions. You could say the same for the development related topic, you just need to follow Gerrit, but this is not how the community decided back then about that process. I like the community decision about this very much, and I would like to see the same happening about the releases. If you don't read all the IRC channels and follow all changes in Gerrit and read all mailing lists, you WILL miss stuff. There's no way around that. I'm not saying you should do that -- I certainly don't. I only expect that major decisions get posted to the mailing list. Removing the bzip2 package was *not* a major decision. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On sexta-feira, 31 de agosto de 2012 14.05.51, Peter Kümmel wrote: On 30.08.2012 13:23, lars.kn...@nokia.com wrote: Hi everybody, the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt-5-beta-is-here/ Enjoy! Lars Where should bugs be reported? Only in Jira? Or also(only?) a post to this list? I'll leave it up to you. We don't want the list flooded with bug reports of all types, but certain severe ones can be posted, especially if they involve build issues. Still, note that an email might go unanswered and forgotten. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On 31/08/2012 07:29, ext Thiago Macieira wrote: On sexta-feira, 31 de agosto de 2012 13.08.39, Laszlo Papp wrote: First: no, that is not true. We will store the upstream tarball as bz2 on the Community OBS anyway due to the debian tools and technology on the community OBS what we have. It's your choice to unpack and repack. Most recent systems handle untar'ing of xz without problem. Instead of 'tar xj' which you use for bzip2, you do 'tar xJ' instead of xz files. Second: premature disk space optimization is not a problem for us, but the RAM usage is. The small size has a price. gzip has a smaller memory footprint than them all. And really, maximum memory usage for decompression of xz at -9 is 80MB. (Compression is 10x that.) Not sure at what level we compress it, but I guess we can tweak that to some lower level without affecting the outcome too much. -8 uses 40MB max, and -7 uses 20MB max, with -6 at only 10MB. I am sorry, but I cannot (and do not wish) hang around IRC all the day along, and filter for gerrit is suboptimal for community discussions. You could say the same for the development related topic, you just need to follow Gerrit, but this is not how the community decided back then about that process. I like the community decision about this very much, and I would like to see the same happening about the releases. If you don't read all the IRC channels and follow all changes in Gerrit and read all mailing lists, you WILL miss stuff. There's no way around that. I'm not saying you should do that -- I certainly don't. I only expect that major decisions get posted to the mailing list. Removing the bzip2 package was *not* a major decision. It's not, with gzip and xz you have a choice of either maximum compatibility or maximum compression (shorter download time anyone?). The choice is yours. And there's two aspects we really care about from a distribution point of view: 1) That everyone can get a hold of the sources (gzip/zip), and 2) That the resources needed to get the sources is minimal (xz/7z) (many Qt developers don't sit on high-speed broadband connections, remember that). Anyone with other special needs can do the repacking locally. Remember that 7z was fairly unknown at one point too, but has caught on due to its extremely powerful compression, and is now well known and accessible anywhere. I'd say it's becoming defacto standard that people install 7zip instead of WinZip on Windows these days. It's certainly the first thing I install on a fresh Windows installation. -- .marius ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
From: marius.storm-ol...@nokia.com marius.storm-ol...@nokia.com Subject: Re: [Development] Qt 5 beta On 31/08/2012 07:29, ext Thiago Macieira wrote: Remember that 7z was fairly unknown at one point too, but has caught on due to its extremely powerful compression, and is now well known and accessible anywhere. I'd say it's becoming defacto standard that people install 7zip instead of WinZip on Windows these days. It's certainly the first thing I install on a fresh Windows installation. I usually put it on installs too; but not b/c of it's powerful compression. I think 7zip really caught on b/c it supported numerous formats - all the well used ones for the open source folks (bzip2, gzip, lzma, ar, etc) and those popular but generally proprietary ones (zip and rar), and on top of it all ran on multiple platforms. So they had a usefulness beyond their primary compression format (7z). Add to it WinZip tightening up their demo licenses (which people historically ignored the 30 days limit on), and you have (in the US at least) a situation prime for a new player that 7zip filled nicely; and since they're open source it was an easy sell. Ben ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
First: no, that is not true. We will store the upstream tarball as bz2 on the Community OBS anyway due to the debian tools and technology on the community OBS what we have. It's your choice to unpack and repack. It is our choice, and many others' choice. It would be in my opinion a way approach (especially if there are no space constraints) to solve this centrally in one place than at many clients'. Second: premature disk space optimization is not a problem for us, but the RAM usage is. The small size has a price. gzip has a smaller memory footprint than them all. That does not mean bz2 does not have smaller than xz. Our and many others' optimal solution is bz2 technology, maintainance, size and memory footprint wise. Thirdly: The conversion is very slow in scratchbox which the developers use locally and also on the build server. Don't convert then. Use the .gz file. I would not need to convert with bz2 either. Moreover, we have an open process for discussing development related issues on the development mailing list, and I would personally propose to have that for the release process as well. We have that. But this was a minor issue. I certainly did not expect it to become this major a sore point. It is a major point to discuss an interface change, especially if that interface is used by many clients and they have to deal with. It is not an internal refactoring that does not effect the clients. I am sorry, but I cannot (and do not wish) hang around IRC all the day along, and filter for gerrit is suboptimal for community discussions. You could say the same for the development related topic, you just need to follow Gerrit, but this is not how the community decided back then about that process. I like the community decision about this very much, and I would like to see the same happening about the releases. If you don't read all the IRC channels and follow all changes in Gerrit and read all mailing lists, you WILL miss stuff. There's no way around that. Please always try to bring up the topics in the future to the relevant mailing list when you intend to change the client interface. Laszlo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
31.08.2012, 15:54, Thiago Macieira thiago.macie...@intel.com: Finally, this *was* a subjective choice: mine. I want to drive adoption of newer, better technology. LZMA is a great improvement over the compression technologies used so far and the xz format is getting interesting adoption. LZMA really is a great improvement over the compression if we talk about compression of binaries. It's undoubtfully *the best* available open source compression algorithm here. But for source archives difference with bz2 is not so drastic. Many thanks to Julian Seward for bzip2 (among other projects he's contributed to), but xz is producing smaller packages nowadays. So, I'd say that our position is: stop complaining and upgrade. If you can't upgrade, there's .gz and you'll pay the penalty by increased disk space in your system. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Regards, Konstantin ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On sexta-feira, 31 de agosto de 2012 19.11.47, Laszlo Papp wrote: Please always try to bring up the topics in the future to the relevant mailing list when you intend to change the client interface This is not client interface. This is just one of the three available compression schemes. It's not major. I stand by the decision and the way it was made. It's a completely minor thing. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt 5 beta
Hi everybody, the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! Lars ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
Someone wrote: [...] blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here A slightly more verbose version is to be found at http://labs.qt.nokia.com/2012/08/30/qt-5-beta-is-here/ Andre' ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On quinta-feira, 30 de agosto de 2012 11.23.07, lars.kn...@nokia.com wrote: Hi everybody, the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! As pointed out on IRC: it's unacceptable that this release happened without a formal GO/NO-GO in the releasing mailing list and in the #qt-releases channel. There are people testing packages today, right now. We might be missing the Release Manager, recognised by the Qt Project, who makes the call and ensures that everyone's opinions are collected. But that doesn't give someone else the right to release. It simply makes a release impossible. Now the deed is done and let's move on. But let's make sure it never happens again. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On Thursday, August 30, 2012 13:41:42 Thiago Macieira wrote: On quinta-feira, 30 de agosto de 2012 11.23.07, lars.kn...@nokia.com wrote: Hi everybody, the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! As pointed out on IRC: it's unacceptable that this release happened without a formal GO/NO-GO in the releasing mailing list and in the #qt-releases channel. There are people testing packages today, right now. We might be missing the Release Manager, recognised by the Qt Project, who makes the call and ensures that everyone's opinions are collected. But that doesn't give someone else the right to release. It simply makes a release impossible. Now the deed is done and let's move on. But let's make sure it never happens again. I agree with all of this. Thanks, -- Stephen Kelly stephen.ke...@kdab.com | Software Engineer KDAB (Deutschland) GmbH Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On Thursday, August 30, 2012 11:23:07 lars.kn...@nokia.com wrote: Hi everybody, the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! Lars 1cebd906af95e2c8ae37f1eae4a1c5019640b3b3 has been tagged as v5.0.0-beta1. That is not the correct commit to have that tag. That is the current HEAD commit in master, not the commit that qt5.git uses as a submodule, and not the commit that is in packages. Thanks, -- Stephen Kelly stephen.ke...@kdab.com | Software Engineer KDAB (Deutschland) GmbH Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On Aug 30, 2012, at 1:41 PM, ext Thiago Macieira thiago.macie...@intel.com wrote: On quinta-feira, 30 de agosto de 2012 11.23.07, lars.kn...@nokia.com wrote: Hi everybody, the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! As pointed out on IRC: it's unacceptable that this release happened without a formal GO/NO-GO in the releasing mailing list and in the #qt-releases channel. There are people testing packages today, right now. We might be missing the Release Manager, recognised by the Qt Project, who makes the call and ensures that everyone's opinions are collected. But that doesn't give someone else the right to release. I have actually talked with quite a few people before making the call. Given that we don't currently have a recognised release manager I took that onto me. I agree we need to make this transparent though, and I'll make sure that happens for the next one. Lars It simply makes a release impossible. Now the deed is done and let's move on. But let's make sure it never happens again. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On 08/30/2012 01:48 PM, ext Stephen Kelly wrote: 1cebd906af95e2c8ae37f1eae4a1c5019640b3b3 has been tagged as v5.0.0-beta1. That is not the correct commit to have that tag. That is the current HEAD commit in master, not the commit that qt5.git uses as a submodule, and not the commit that is in packages. Thanks, Hi, The tag in qtbase should be updated now. It points to 62b0f41ae0c2971db5d6e53972d746b0a865a736 Cheers, -- Sergio Ahumada ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
ext Thiago Macieira wrote on 2012-08-30: On quinta-feira, 30 de agosto de 2012 11.23.07, lars.kn...@nokia.com wrote: Hi everybody, the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! As pointed out on IRC: it's unacceptable that this release happened without a formal GO/NO-GO in the releasing mailing list and in the #qt-releases channel. There are people testing packages today, right now. We might be missing the Release Manager, recognised by the Qt Project, who makes the call and ensures that everyone's opinions are collected. But that doesn't give someone else the right to release. It simply makes a release impossible. Now the deed is done and let's move on. But let's make sure it never happens again. Agreed. The latest test of the windows source package was reported as a failure (by J-P Nurmi), so the beta might not even work for win32-msvc2010 mkspec. Jan Arve ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
Greetings all, Le 30/08/2012 13:23, lars.kn...@nokia.com a écrit : the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! Trying to compile on Windows 7 64bits using MSVC 2010 (32bits compiler). After having read the provided README. D:\qt\qt5-5.0.0-win32-msvc2010configure -help + D:/qt/qt5-5.0.0-win32-msvc2010/qtbase/configure -help Please wait while bootstrapping configure ... Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. cl -c -Yc -nologo -Zm200 -Zc:wchar_t -MT -W3 -GR -EHsc -w34100 -w34189 -DUNICODE -DQT_NO_CODECS -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_LITE_COMPO NENT -DQT_NO_COMPRESS -DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT -D_CRT_SECURE_NO_DEPRECATE -DQT_BOOTSTRAPPED -DCOMMERCIAL_VERSION -I..\..\include -I ..\..\include\QtCore -I..\..\include\QtCore\5.0.0 -I..\..\include\QtCore\5.0.0\QtCore -ID:\qt\qt5-5.0.0-win32-msvc2010\qtbase\tools\shared -ID:\qt\qt5- 5.0.0-win32-msvc2010\qtbase\mkspecs\win32-msvc2008 -Fpconfigure_pch.pch -Foconfigure_pch.obj -TP D:\qt\qt5-5.0.0-win32-msvc2010\qtbase\tools\configure\configur e_pch.h configure_pch.h D:\qt\qt5-5.0.0-win32-msvc2010\qtbase\tools\configure\configure_pch.h(49) : fatal error C1083: Cannot open include file: 'qlist.h': No such file or directory NMAKE : fatal error U1077: 'C:\vs10\VC\BIN\cl.EXE' : return code '0x2' Stop. *** qtbase/configure exited with non-zero status. ...and some others, missing QtCore/qalgorithms.h... - Added to -I..\..\src\corelib\tools to EXTRA_CXXFLAGS - Changed ...\qtbase\src\corelib\tools\qlist.h to #include qalgorithms.h instead of QtCore/qalgorithms.h ...and more errors like those ones... Giving up for now. However if someone want me to try something I'll be glad to try, I just don't have time to dig myself. *sigh* -- /- Yves Bailly - Software developper -\ \- Sescoi RD - http://www.sescoi.fr -/ The possible is done. The impossible is being done. For miracles, thanks to allow a little delay. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
ext Yves Bailly wrote on 2012-08-30: Greetings all, Le 30/08/2012 13:23, lars.kn...@nokia.com a écrit : the Qt 5 beta has now been released. Please find all the details at http://www.qt-project.org/wiki/Qt-5-Beta and my blog post at http://labs.qt.nokia.com/2012/08/30/qt5-beta-is-here Enjoy! Trying to compile on Windows 7 64bits using MSVC 2010 (32bits compiler). After having read the provided README. D:\qt\qt5-5.0.0-win32-msvc2010configure -help + D:/qt/qt5-5.0.0-win32-msvc2010/qtbase/configure -help Please wait while bootstrapping configure ... Microsoft (R) Program Maintenance Utility Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. cl -c -Yc -nologo -Zm200 -Zc:wchar_t -MT -W3 -GR -EHsc -w34100 -w34189 -DUNICODE -DQT_NO_CODECS -DQT_NO_TEXTCODEC - DQT_NO_UNICODETABLES -DQT_LITE_COMPO NENT -DQT_NO_COMPRESS - DQT_NO_THREAD -DQT_NO_QOBJECT -DQT_NO_GEOM_VARIANT - D_CRT_SECURE_NO_DEPRECATE -DQT_BOOTSTRAPPED -DCOMMERCIAL_VERSION - I..\..\include -I ..\..\include\QtCore - I..\..\include\QtCore\5.0.0 -I..\..\include\QtCore\5.0.0\QtCore -ID:\qt\qt5-5.0.0-win32-msvc2010\qtbase\tools\shared -ID:\qt\qt5- 5.0.0-win32-msvc2010\qtbase\mkspecs\win32-msvc2008 - Fpconfigure_pch.pch -Foconfigure_pch.obj -TP D:\qt\qt5-5.0.0-win32- msvc2010\qtbase\tools\configure\configur e_pch.h configure_pch.h D:\qt\qt5-5.0.0-win32- msvc2010\qtbase\tools\configure\configure_pch.h(49) : fatal error C1083: Cannot open include file: 'qlist.h': No such file or directory NMAKE : fatal error U1077: 'C:\vs10\VC\BIN\cl.EXE' : return code '0x2' Stop. *** qtbase/configure exited with non-zero status. ...and some others, missing QtCore/qalgorithms.h... - Added to -I..\..\src\corelib\tools to EXTRA_CXXFLAGS - Changed ...\qtbase\src\corelib\tools\qlist.h to #include qalgorithms.h instead of QtCore/qalgorithms.h ...and more errors like those ones... Giving up for now. However if someone want me to try something I'll be glad to try, I just don't have time to dig myself. *sigh* configure.bat will run perl. Please check if it will use the ActiveState perl, and not the perl shipped with msysgit. I always put the ActiveState perl directory as the first path in %PATH% in order to avoid this. Jan Arve ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
Le 30/08/2012 14:43, jan-arve.saet...@nokia.com a écrit : ext Yves Bailly wrote on 2012-08-30: configure.bat will run perl. Please check if it will use the ActiveState perl, and not the perl shipped with msysgit. I always put the ActiveState perl directory as the first path in %PATH% in order to avoid this. I guess it's actually ActiveState's Perl indeed: D:\qtperl --version This is perl 5, version 14, subversion 2 (v5.14.2) built for MSWin32-x64-multi-thread (with 1 registered patch, see perl -V for more detail) Copyright 1987-2011, Larry Wall Binary build 1402 [295342] provided by ActiveState http://www.ActiveState.com Built Oct 7 2011 15:19:36 Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using man perl or perldoc perl. If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. -- /- Yves Bailly - Software developper -\ \- Sescoi RD - http://www.sescoi.fr -/ The possible is done. The impossible is being done. For miracles, thanks to allow a little delay. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On Thursday, August 30, 2012 01:41:42 PM ext Thiago Macieira wrote: [...] Now the deed is done and let's move on. But let's make sure it never happens again. Sounds right. I hope everyone also agrees that it's time to celebrate! We've come a bloody long way since the Alpha. If we keep up the pace perhaps we can make another release soon, which will fix many of the glitches of this beta. Simon ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On 30.8.2012 16.20, Simon Hausmann simon.hausm...@nokia.com wrote: I hope everyone also agrees that it's time to celebrate! We've come a bloody long way since the Alpha. +1 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On quinta-feira, 30 de agosto de 2012 15.20.33, Simon Hausmann wrote: If we keep up the pace perhaps we can make another release soon, which will fix many of the glitches of this beta. I'm all for making more periodic releases. Congrats to everyone who has put effort into making this happen. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On quinta-feira, 30 de agosto de 2012 16.59.13, Laszlo Papp wrote: I am wondering, if it was possible to get .bz2 tarballs as well? This is a preferred format at times for packagings. We were doing them until the day before yesterday. Discussing yesterday, we decided that it wasn't worth the disk space to have all three of .tar.xz, .tar.bz2 and .tar.gz. On my suggestion, we dropped .tar.bz2. We're keeping .tar.gz to ensure maximum compatibility and .tar.xz because it's the smaller of the three. I'd rather not bring back .tar.bz2. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On Thu, Aug 30, 2012 at 5:08 PM, Thiago Macieira thiago.macie...@intel.comwrote: On quinta-feira, 30 de agosto de 2012 16.59.13, Laszlo Papp wrote: I am wondering, if it was possible to get .bz2 tarballs as well? This is a preferred format at times for packagings. We were doing them until the day before yesterday. Discussing yesterday, we decided that it wasn't worth the disk space to have all three of .tar.xz, .tar.bz2 and .tar.gz. On my suggestion, we dropped .tar.bz2. We're keeping .tar.gz to ensure maximum compatibility and .tar.xz because it's the smaller of the three. I'd rather not bring back .tar.bz2. It is ok, if the space is (can be) a bottleneck. Laszlo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
- Original Message - From: Thiago Macieira thiago.macie...@intel.com To: development@qt-project.org Sent: Thursday, August 30, 2012 1:07 PM Subject: Re: [Development] Qt 5 beta On quinta-feira, 30 de agosto de 2012 17.30.58, Laszlo Papp wrote: I'd rather not bring back .tar.bz2. It is ok, if the space is (can be) a bottleneck. It's another 350 MB. We can offer it, but is there really the need? Can't you use .tar.xz instead? tar.bz2 is pretty common, along with tar.gz. tar.xy, OTOH, is quite rare. Googling tar.bz2 yields good results what to do with such a file. Googling tar.xy yields nothing useful about what compression engine is used even used; Googling compressed file extensions yielded Wikipedia's list of archive formats which finally produced some useful info - that it's an LZMA2 compression. While I understand that tar.xy may be smaller it's use general use seems to be limited so unless there is a supported platform/target that only uses tar.xy, I'd suggest dropping it and keeping tar.bz2 instead. Given a choice between a bzip and gzip, I'd personally choose bzips. If space is a concern, then zip and tar.gz are probably sufficient for distribution. $0.02 Ben ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
tar.bz2 is pretty common, along with tar.gz. tar.xy, OTOH, is quite rare. Googling tar.bz2 yields good results what to do with such a file. Googling tar.xy yields nothing useful about what compression engine is used even used; Googling compressed file extensions yielded Wikipedia's list of archive formats which finally produced some useful info - that it's an LZMA2 compression. While I understand that tar.xy may be smaller it's use general use seems to be limited so unless there is a supported platform/target that only uses tar.xy, I'd suggest dropping it and keeping tar.bz2 instead. +1. Selecting xz, but not bz2 is a suboptimal decision in my opinion. I would personally even go further with this, if there is no space contraints for about 350 MB for such releases like this: it would be nice to distribute all those three formats because each of them may be used by several distributions and individuals. bz2 may be used by Ubuntu, Debian, Harmattan, Fremantle, debian based raspberry pi, ubuntu arm based beagleboard and so forth. They can also use tar.gz as far as I know, but at least for Harmattan we packagers for sure prefer the bz2 variant. xz may be used for Archlinux, Chakra, Frugalware, and so forth. I do not personally see (apart from space limitations) why only certain distribution formats would be dropped from the aforementioned, but others not. It would not be too fair in my opinion. Even if any of those is dropped, I would not drop the debian based preference because of the common usage of the bz2 format here and there. Laszlo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On Thursday 30 August 2012 11:48:38 BRM wrote: tar.bz2 is pretty common, along with tar.gz. tar.xy, OTOH, is quite rare. Googling tar.bz2 yields good results what to do with such a file. Googling tar.xy yields nothing useful about what compression engine is used even used; Googling compressed file extensions yielded Wikipedia's list of archive formats which finally produced some useful info - that it's an LZMA2 compression. While I understand that tar.xy may be smaller it's use general use seems to be limited so unless there is a supported platform/target that only uses tar.xy, I'd suggest dropping it and keeping tar.bz2 instead. Given a choice between a bzip and gzip, I'd personally choose bzips. If space is a concern, then zip and tar.gz are probably sufficient for distribution. $0.02 Ben I'm not sure wether it's just a typo, but you consistently write .xy so I'm going to assume not. Also, first and third tar.xz results in google for me are: http://ubuntuforums.org/showthread.php?t=1116012 http://en.wikipedia.org/wiki/Xz Not being a packager I don't know, but I have a hard time imagining it's harder to change your packaging scripts from Qt4 to Qt5 than from tar.bz2 to tar.xz. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
Not being a packager I don't know, but I have a hard time imagining it's harder to change your packaging scripts from Qt4 to Qt5 than from tar.bz2 to tar.xz. 1) This could be said vice versa, so not fair to say. 2) We have had bz2 previously (as well) and we were able to package with bz2, so this could potentially be changing for people from what was working. 3) Why another change in the first place, if there are no space limitations? 4) Just one random example of those: when I mentioned this to one of friends today he was asking what xz exactly. That person was aware of the other formats. He has also made some packagings already for Harmattan, so not quite a newcomer. I know, this could happen vice versa, so not fair to say... That is why I think, it is ok to keep both, or the more common bz2 format, if we are really short with space. Laszlo ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
On quinta-feira, 30 de agosto de 2012 21.10.16, Laszlo Papp wrote: Not being a packager I don't know, but I have a hard time imagining it's harder to change your packaging scripts from Qt4 to Qt5 than from tar.bz2 to tar.xz. 1) This could be said vice versa, so not fair to say. 2) We have had bz2 previously (as well) and we were able to package with bz2, so this could potentially be changing for people from what was working. 3) Why another change in the first place, if there are no space limitations? Because LZMA produces smaller files. I'd like to increase adoption of it. So let me put it this way: upgrade or go back to gzip. 4) Just one random example of those: when I mentioned this to one of friends today he was asking what xz exactly. That person was aware of the other formats. He has also made some packagings already for Harmattan, so not quite a newcomer. I know, this could happen vice versa, so not fair to say... That is why I think, it is ok to keep both, or the more common bz2 format, if we are really short with space. I disagree. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden signature.asc Description: This is a digitally signed message part. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt 5 beta
From: Jonas M. Gastal jgas...@profusion.mobi To: development@qt-project.org; BRM bm_witn...@yahoo.com Sent: Thursday, August 30, 2012 4:02 PM Subject: Re: [Development] Qt 5 beta On Thursday 30 August 2012 11:48:38 BRM wrote: tar.bz2 is pretty common, along with tar.gz. tar.xy, OTOH, is quite rare. Googling tar.bz2 yields good results what to do with such a file. Googling tar.xy yields nothing useful about what compression engine is used even used; Googling compressed file extensions yielded Wikipedia's list of archive formats which finally produced some useful info - that it's an LZMA2 compression. While I understand that tar.xy may be smaller it's use general use seems to be limited so unless there is a supported platform/target that only uses tar.xy, I'd suggest dropping it and keeping tar.bz2 instead. Given a choice between a bzip and gzip, I'd personally choose bzips. If space is a concern, then zip and tar.gz are probably sufficient for distribution. $0.02 Ben I'm not sure wether it's just a typo, but you consistently write .xy so I'm going to assume not. Also, first and third tar.xz results in google for me are: http://ubuntuforums.org/showthread.php?t=1116012 http://en.wikipedia.org/wiki/Xz Not being a packager I don't know, but I have a hard time imagining it's harder to change your packaging scripts from Qt4 to Qt5 than from tar.bz2 to tar.xz. A typo and misreading on my part. And yes, correcting that does yield more pertinent information. I'd still argue it is good to keep tar.bz2. Ben ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
