From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: otavio.salvador@ossystems.com.br
Subject: Re: [meta-qt5] Update master to Qt 5.7 release
Date: Wed, 29 Jun 2016 11:24:02 +0200 [thread overview]
Message-ID: <20160629092402.GA2558@jama> (raw)
In-Reply-To: <64fedf2a-0ac7-1c88-fb2e-132ad5cd5690@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
On Wed, Jun 29, 2016 at 07:59:04AM +0200, Pascal Bach wrote:
> Hello
>
>
> The meta-qt5 master is currently on a pre release of 5.7.
> I would like to update it to the final Qt 5.7 release.
>
> I saw that the commit of the latest update involved a lot of changes across many files including updates of patches.
>
> Now before I go and try to change everything manually, I want to ask how this is usually done?
> Is there a script or something?
There isn't a script as such, just bunch of bash snippets in my bash
history.
There are forks of couple qt* repositories in github.com/meta-qt5 for
most modules which have many or more complicated patch files applied in
meta-qt5 recipes.
Then I rebase e.g. b5.7 branch in each of them, use git format-patch to
refresh the patches and update SRCREV in the recipe based on upstream
5.7 branch I've rebased on. Then at least build test all recipes in meta-qt5
(I use only small part of meta-qt5 on any devices I own).
Otavio said he will be working on next upgrade, I haven't seen any patch
yet, but maybe there is some wip on his side.
Similarly with 5.6.1 in krogoth branch, there was some incomplete
pull-request on github, but I haven't seen any patch on this ML yet.
I'm busy with some other stuff, so I don't plan to do it myself soon.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-06-29 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 5:59 [meta-qt5] Update master to Qt 5.7 release Pascal Bach
2016-06-29 9:24 ` Martin Jansa [this message]
2016-06-29 11:41 ` Otavio Salvador
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=20160629092402.GA2558@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.