Hello
I wonder if you plan to release your OpenEmbedded patches? I would really like to see an "open" repository, where users of the taskit OpenEmbedded have access to the package files, patches, additional scripts etc. I have built my own OpenEmbedded environment for my own development using the panelcard, but I would rather like to merge my work with yours if there is a possibility. There won't be a simple solution I guess, as the the requirements are different, but we could at least start a discussion and see where it goes. For me, and I guess there are other users too, it's just not sufficient to have access to binary packages, especially if you work on a product you have to support years from now.
What do you think?
Re: OpenEmbedded Patches
Currently we are basing our work on the OpenEmbedded stable branch. We thought about releasing a patch or a patch series against it when we have a final release, but it is also possible to release the current work earlier if desired.
My work is currently based on
My work is currently based on the openembedded dev branch, but i'm moving over to the stable branch as well. So i'm definitely interested in your work-in-progress patches. If possible please mail your current patch series to [simon dot kallweit at intefo dot ch], thanks! But my question remains, do you plan to offer some kind of open repository so other developers like me could post their work? I think that would be really great. As you probably know, i could commit some patches for uboot-1.3 for example. Also i have ported your kernel patches to use the newest 2.6.25 kernel. Any ideas?
Currently we maintain our
Currently we maintain our work with OpenEmbedded in a git-tree. We are not completely closed to the idea of maintaining a public version were other users can push their work into. Communication could take place via this forum. We will post our patch series later this day.
In regard to other work, we think that a new forum, where everybody can post his works along with files would more fitting. Honestly, I don't think this will get an overused section.
In general we are not planning to change our current release policy of supporting a specific kernel version for longer periods of time, as we want to offer our users a stable, not ever changing interface.
That said, we don't have any problems if other developers want to use their own, newer versions of the kernel, and it is not our concern to constrict availability. But again, our manpower is limited we are definitely not able to support every single version.
Finally, any other peoples opinions on this topic would be really nice.
Current patches
I have just uploaded our current work as a patch series. You can find these patches in our download section.