On Mon, Jan 11, 2010 at 01:26:53PM +0100, Patryk Benderz wrote:
> [cut moaning]
> > -Not trying to defend ourselves or anything, but keep in mind that SHR 
> > is not Debian with >1000 active devs. We derive from a highly unstable 
> > distribution (OpenEmbedded development tree), and much of that is 
> > outside our control. So stuff changing and disappearing might not always 
> > be our fault, we cannot check every change that goes into OpenEmbedded 
> > and we don't have the rights to veto those that we don't like.
> I get your point, but what about deriving from stable branch of OE? Is
> it out of consideration?

When last stable branch of OE was created, there was no SHR support 
(distribution
configs, our recipes).

I've merged last few diffs to org.openembedded.dev branch about a week
ago (still few minor changes are only in shr/merge see my e-mail about
shr/merge branch status).

We hope to get SRCPV merged to oe.dev before stable/2010 is branched
from .dev and start building shr-testing/shr-stable from stable/2010
and shr-unstable directly from org.openembedded.dev.

This will eliminate annoying workflow overhead we now have (every commit
goes to oe.dev, then it should be merged to srcpv branch, then srcpv branch 
is merged to shr/merge).

Regards,
-- 
uin:136542059                jid:[email protected]
Jansa Martin                 sip:[email protected] 
JaMa                         
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel

Reply via email to