[yocto] [dora] x264: Update SRCREV to match commit in upstream git repo

Paul Eggleton paul.eggleton at linux.intel.com
Tue Jun 17 09:46:49 PDT 2014


On Tuesday 17 June 2014 11:31:52 Patrick Doyle wrote:
> Thanks Paul,
> I hope I didn't step on any toes with this.  

No, not at all; I just wanted to let you know we are working on the issue.

> I'm still confused about what parts of the project are "Yocto" and 
> what parts are "OE".

Right, I know it's not as clear as it could be sometimes. At least for 
patches, FYI we did put some "where to send patches" information in the README 
file within the Poky repository. (We're certainly open to suggestions on making 
the process easier, be it from a documentation, tooling or process angle.)
 
> Do you have any guesses as to when this might show up in the official
> dora branch?

So Robert is the dora branch maintainer and he's replied separately; it should 
be fairly quick now that he's aware of it.

> I am asking because we have a development flow here (I'm still not
> sure I'm 100% happy with it, but it's what we've got), where we mirror
> the poky repository, check out from that mirror very occasionally, and
> generate a complete-from-scratch even more occasionally.
> Unfortunately, we have a situation right now where, if somebody were
> to do that (say, hypothetically speaking, a new person joins the
> team), we can't generate a complete build from scratch.  I could apply
> my patch to our local mirror, and thus break the mirror.  Or I could
> create a local clone of the mirror and reference our local clone.  Or
>> 
> If this will show up in dora in a matter of hours to a day or so, I'm
> going to stop thinking about this.  If it is anticipated that it will
> take longer, then I'll come up with a solution.
> 
> I'm not trying to complain nor advocate that this patch get applied
> faster than would be normal, I'm just trying to plan my day :-)

No problem - in this particular instance with x264 it was a bit of an 
unfortunate trifecta where the upstream project does not provide release 
tarballs so we build directly from their git repository; they recently decided 
to rewrite their git history without telling anyone, and we didn't notice 
immediately because we don't build it on our autobuilder regularly (since it 
has LICENSE_FLAGS set). Even when we did know about it though, it's fair to 
say we have been a little slow to correct for it; hopefully we can get this 
patch in soon and then it'll be taken care of, at least for the x264 recipes 
in master, daisy and dora.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



More information about the yocto mailing list