[Development] New Qt5.4 snapshot available

Heikkinen Jani jani.heikkinen at theqtcompany.com
Wed Oct 29 10:44:58 CET 2014


Yes, it is possible. But as said earlier we have limited amount of disc space and that’s why we don’t offer sources automatically for each snapshot. On the other hand I have promised to copy sources to that snapshot which I want to be tested. I know I have usually forgot to do that, sorry. I’ll try to do it in the future…
Br,
Jani

From: development-bounces+jani.heikkinen=theqtcompany.com at qt-project.org [mailto:development-bounces+jani.heikkinen=theqtcompany.com at qt-project.org] On Behalf Of Alex Montgomery
Sent: 27. lokakuuta 2014 19:28
To: Thiago Macieira
Cc: development at qt-project.org
Subject: Re: [Development] New Qt5.4 snapshot available

Are source packages somehow harder to make than packages for particular platforms? Many of the people who would bother trying out a beta have special needs like maintaining their own patches or static linking and it is annoying to have to resort to git. Would it be possible to make source packages available at every stage of the beta release process?

On Mon, Oct 27, 2014 at 8:37 AM, Thiago Macieira <thiago.macieira at intel.com<mailto:thiago.macieira at intel.com>> wrote:
On Monday 27 October 2014 13:50:03 Joerg Bornemann wrote:
> I3f0739b279123e0a049d52da455f40ad1a20b4ab is the change id in gerrit.
> The corresponding commit id is 86f7d9ce9873b5c6897e99763aba5765640ceba3.
>
> git checkout 86f7d9ce9873b5c6897e99763aba5765640ceba3
> git submodule update

Or:

git checkout :/I3f0739b279123e0a049d52da455f40ad1a20b4ab
--
Thiago Macieira - thiago.macieira (AT) intel.com<http://intel.com>
  Software Architect - Intel Open Source Technology Center

_______________________________________________
Development mailing list
Development at qt-project.org<mailto:Development at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20141029/4cd11d67/attachment.html>


More information about the Development mailing list