<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 29, 2013 at 11:47 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, 2013-05-29 at 16:37 +0200, Martin Jansa wrote:<br>
> On Wed, May 29, 2013 at 08:51:36AM -0500, Mark Hatle wrote:<br>
> > Background:<br>
> ><br>
> > At the recent TSC meeting we were discussing ways of removing the PRINC<br>
> > in favor of the PR server, which should now be standard. The first step<br>
> > in this process is coming up with a simple patch that declared PRINC as<br>
> > deprecated. If this type of patch is successful, the block of code could<br>
> > be replaced with a bb.error eventually.<br>
> ><br>
> > It is not expected that this patch will go in by itself, but instead<br>
> > should be coordinated with changes to the recipes in common layers such<br>
> > as openembedded-core, meta-openembedded/meta-* and other community layers.<br>
><br>
> This doesn't say what's the process of getting all PR increments<br>
> applied.<br>
><br>
> Should we send list of recipes and required PR increments per layer (and<br>
> someone will sum these increments and create actual PR bump from it). Or<br>
> will we take turns and send actual PR bump patches per layer and someone<br>
> will define order of layers to go in (so that we prevent many conflicts<br>
> while merging)?<br>
<br>
</div>This is something we need to figure out. The realistic process is<br>
probably do this layer by layer. If we can batch some up together that<br>
would obviously be better...<br></blockquote><div><br></div><div style>If this is the case, to ensure we have the PR in sync we should have it PRINC as a bb.error; this will cause some pain but will avoid PRServer picking the layer PRINC and losing it in next build. Or does PRServer handle this gracefully?</div>
<div style><br></div><div style>Regards,</div><div> </div></div>-- <br>Otavio Salvador O.S. Systems<br><a href="http://www.ossystems.com.br" target="_blank">http://www.ossystems.com.br</a> <a href="http://projetos.ossystems.com.br" target="_blank">http://projetos.ossystems.com.br</a><br>
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750<br>
</div></div>