[oe] [meta-qt5] Dropping tarball recipes from meta-qt5
Paul Eggleton
paul.eggleton at linux.intel.com
Thu May 28 10:49:22 UTC 2015
On Thursday 28 May 2015 12:46:33 Andreas Müller wrote:
> On Thu, May 28, 2015 at 12:36 PM, Martin Jansa <martin.jansa at gmail.com>
wrote:
> > I'm still working on finishing 5.5-beta1 recipes for qt5, I'm getting
> > tired of maintaining 2 sets of patches and 2 versions of recipes in the
> > same layer branch.
> >
> > 1) Would people mind dropping 5.4 support in master branch (who wants to
> > use 5.4 can continue to use "fido" branch of meta-qt5, there are patches
> > for 5.4.2 git recipes as well).
>
> As soon as 5.5 is out I have no problem.
>
> > 2) Would people mind having only git recipes? It will be easier to
> > update them. Only disadvantages I can think of are the need to clone
> > from git and not being aligned with exact release for long time (git
> > recipes usually track newer revisions in e.g. 5.4 branch than 5.4.0 or
> > 5.4.1 tarbal recipes.
>
> Advantage for me would be that recipe-wise changing versions for test
> is easier - so no I appreciate.
Indeed, it sounds reasonable. My only question though would be is there a
significant penalty in terms of do_fetch time? We've had complaints about other
recipes that fetch large git repos taking ridiculously long to fetch.
> > If we all use the same version from the same recipes then we can test it
> > better and it will be much easier to maintain.
>
> I think it's time to mention: Thanks for maintaining qt5 and other
> layers - you do an excellent job!
Seconded!!
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
More information about the Openembedded-devel
mailing list