[OE-core] Proposal: Creating meta-networking

Marko Lindqvist cazfi74 at gmail.com
Sat Jun 16 17:36:59 UTC 2012


On 15 June 2012 22:55, Philip Balister <philip at balister.org> wrote:
> On 06/15/2012 02:55 PM, Andrei Gherzan wrote:
>> On Fri, Jun 15, 2012 at 9:08 PM, Otavio Salvador <otavio at ossystems.com.br>wrote:
>>
>>> On Fri, Jun 15, 2012 at 12:42 PM, Khem Raj <raj.khem at gmail.com> wrote:
>>>> I think creating a networking layer is fine idea, alongside meta-oe,
>>>> as a separate layer in meta-openembedded repo. Reshuffling recipes
>>>> from meta-oe into different layers is fine. I would like to avoid copies.
>>>
>>> I'd prefer if it used another git repository; people needing to use it
>>> shouldn't be forced to clone whole meta-oe.
>>>
>>> This would be my proposal as well. To have this as a separate layer.
>
> meta-oe already hosts several layers. It is kind of nice not to have to
> clone a slowly increasing number of git repos. Rather clone a few and
> manage the layers within them.

 Need to clone many separate repos for building your own system
(bitbake, oe-core, oe-meta, oe-networking, your own sw) is a minor
annoyance in itself, but need to synchronize between them (what
revisions of the first repo are compatible with given revision of the
second) could lead to headaches for someone having additional
constraints of the production level system maintenance (i.e. when one
cannot simply take HEAD of everything).
 I do see both sides. Either some people need to clone bigger repo
than they absolutely need, or some other people are forced to clone
several repos. Depends on OE userbase which one would annoy more
people.


 - ML




More information about the Openembedded-core mailing list