Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-qt5][PATCH] qt5: Update to Qt 5.11.0
Date: Wed, 20 Jun 2018 15:52:19 +0200	[thread overview]
Message-ID: <67f7d601-e2e7-63c8-ac49-2cf27345853d@zonque.org> (raw)
In-Reply-To: <20180620112953.GA3257@jama>

On Wednesday, June 20, 2018 01:29 PM, Martin Jansa wrote:
> On Wed, Jun 20, 2018 at 12:50:52PM +0200, Daniel Mack wrote:
>> On Wednesday, June 20, 2018 12:36 PM, Martin Jansa wrote:
>>> It's already in meta-qt5/master with couple fixes on top of that.
>>
>> Ah, sorry. For some reason, I only looked into the -next branches.
> 
> Well, meta-qt5/master-next is exactly the same as meta-qt5/master :).
> 
>> Stupid. FWIW, I have a patch for 5.11.1 ready. Will send once the build
>> succeeded.
> 
> I've started rebasing the patches in meta-qt5 as well, but we cannot use
> 5.11.1 until downmerge to 5.11 is finished, because:
> 
> 1) we cannot use 5.11.1 branch, because they might delete this branch at
> any time (like with 5.10.1)

But there's also a v5.11.1 tag, which is unlikely to be deleted?

I might miss something and I haven't followed the discussions, but is 
your idea to drop the explicit SRCREVs in the recipes in favor of 
AUTOREV and a branch name?

FWIW, I've written a small shell script that retrieves the SHA1 for each 
of the qt projects and updates the .bb files automatically. That seems 
to work quite well, and I'm happy to share it. There's still the problem 
with downstream patches and other necessary changes in the recipes for 
new Qt versions, but that's an issue either way.


Thanks,
Daniel


  parent reply	other threads:[~2018-06-20 13:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29  9:25 [meta-qt5][PATCH] qt5: Update to Qt 5.11.0 Samuli Piippo
2018-06-06 20:05 ` Martin Jansa
2018-06-08  4:21   ` Samuli Piippo
2018-06-15  5:44     ` Samuli Piippo
2018-06-20 10:07 ` Daniel Mack
2018-06-20 10:36   ` Martin Jansa
2018-06-20 10:50     ` Daniel Mack
2018-06-20 11:29       ` Martin Jansa
2018-06-20 11:57         ` Samuli Piippo
2018-06-20 12:19           ` Martin Jansa
2018-06-20 13:38             ` Samuli Piippo
2018-06-21  5:14             ` Samuli Piippo
2018-06-21  9:03               ` Martin Jansa
2018-06-21  9:55                 ` Samuli Piippo
2018-06-20 13:52         ` Daniel Mack [this message]
2018-06-20 18:06           ` Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67f7d601-e2e7-63c8-ac49-2cf27345853d@zonque.org \
    --to=daniel@zonque.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox