Martin Jansa <[email protected]> writes:
> OE as we use it now, will probably go RO after first oe-core/meta-oe
> release
> http://lists.linuxtogo.org/pipermail/tsc/2011-March/000209.html
>
> So I started to work on oe-core/meta-oe/meta-efl/meta-shr layout,
> almost all needed stuff for oe-core/meta-oe/meta-efl is included
> upstream now.
>
> meta-shr lives now in our repo:
> http://git.shr-project.org/git/?p=meta-shr.git;a=summary
>
> and shr-lite-image for nokia900 finally builds fine (today's build
> probably boots too :))
I'm sorry, but on first reading I'm completely lost here.
Firstly, I feel that I have no way of evaluating whether it's good or
bad for SHR's underlying repository to be frozen (assuming I've
correctly understood that part). On the one hand, software clearly
can't be frozen, because the upstream projects will evolve, and often
SHR will want those new things. On the other hand, OE master (in its
current RW state) feels like it could be too much of a juggernaut, and
that the whims of other OE projects could pull SHR into instability.
How do you/we find a happy medium between those two extremes?
Secondly, I have no idea yet what meta-oe/meta-elf/meta-shr are. But
probably that's for me to go and look some more.
> If you want to give it a try, use:
> make setup-shr-core
> with SHR Makefile or read what it does if you don't like Makefiles.
I'll do that. But could you also describe plainly what shr-core is (or
will be)? Is it intended to replace SHR-U?
Thanks,
Neil
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
