From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: meta-qt5
Date: Mon, 8 Jun 2015 14:21:55 -0400 [thread overview]
Message-ID: <20150608182154.GD32398@edge> (raw)
In-Reply-To: <55759318.1010904@ti.com>
On Mon, Jun 08, 2015 at 09:05:28AM -0400, Jacob Stiffler wrote:
> It appears that the meta-qt5 layer has dropped the 5.4.1 versioned
> recipes. This means that the meta-arago bbappends no longer apply.
>
> I see there is a history of meta-arago using the versioned recipes,
> but these are no longer there, and only the git based recipes
> remain.
>
> I'm not sure of the impact there would be in moving the meta-arago
> appends to the git based recipes. I'll give this a try and provide
> an update later.
Yeah, saw this last week, but haven't had a chance to fix it.
What I'm thinking is there are 2 options:
1. Rename bbappends from 5.4.1 to git - seems to build fine locally here.
2. Lock meta-qt5 on the commit before 5.4.1 got removed - it won't get much
better in 5.4.x branch and we are waiting for 5.5 to get better Touchscreen
support. We can keep using meta-qt5/master in meta-arago/master, but lock
meta-arago/daisy to 5.4.1, which is what has been tested so far. This seems
safer for the release...
Thoughts?
--
Denys
next prev parent reply other threads:[~2015-06-08 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 13:05 meta-qt5 Jacob Stiffler
2015-06-08 18:21 ` Denys Dmytriyenko [this message]
2015-06-08 18:30 ` meta-qt5 Jacob Stiffler
[not found] <CACgAsMeiKrLgjPnsZwOJtncRJ4nKExvjtS23VXNXcwyMsWtaDw@mail.gmail.com>
2014-02-03 17:37 ` meta-qt5 Martin Jansa
2014-02-03 17:43 ` meta-qt5 Gary Thomas
2014-02-07 13:47 ` meta-qt5 Otavio Salvador
2014-02-10 21:22 ` meta-qt5 Denys Dmytriyenko
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=20150608182154.GD32398@edge \
--to=denys@ti.com \
--cc=j-stiffler@ti.com \
--cc=meta-arago@arago-project.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 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.