how do I contribute to yocto
Hello all,
In the process of creating my custom image, I ended up writing new
recipes for packages which does not exist in yocto. I think it will be useful for others. I use the edison branch for my work, and I add the new recipes to my custom layer without disturbing the edison branch. So, how do I contribute these new recipes?
Read the wiki https://wiki.yoctoproject.org/wiki/Contribution_Guidelines
it doesn't mention about the branch to use etc.
Can someone guide me.
Regards
Joshua
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Quoted 11 lines · Joshua Immanuel
Hello all,
In the process of creating my custom image, I ended up writing new
recipes for packages which does not exist in yocto. I think it will be useful for others. I use the edison branch for my work, and I add the new recipes to my custom layer without disturbing the edison branch. So, how do I contribute these new recipes?Read the wiki https://wiki.yoctoproject.org/wiki/Contribution_Guidelines
it doesn't mention about the branch to use etc.Can someone guide me.
Hi Joshua,
I'd put your layer up on a git repo somewhere (GitHub?) and make sure you have a note in your layer's README file that mentions that the layer is intended for use with the edison release.
If you're looking to maintain this layer for multiple releases of Yocto, it may make sense to maintain a similar branch structure - i.e, your master branch aims to build with Poky master, edison branch builds with edison, etc.
Scott
Signature · 3 lines
Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center
Hello Scott,
Quoted 3 lines · Scott Garman
I'd put your layer up on a git repo somewhere (GitHub?) and make sure you have a note in your layer's README file that mentions that the layer is intended for use with the edison release.
But my entire layer won't be useful to everyone, as it contains recipes for my user space applications too. But, there are certain recipes for some useful packages which are not available in edison and master branch. So, how to go about it?
Regards
Joshua
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Quoted 4 lines · Joshua Immanuel
But my entire layer won't be useful to everyone, as it contains recipes for my user space applications too. But, there are certain recipes for some useful packages which are not available in edison and master branch. So, how to go about it?
there are other layers which you could look into and see if those recipe make sense to any of these layers please see
http://www.openembedded.org/wiki/LayerIndex
if not host them in your layer if u wish to maintain them and add your layer to above index
Hello Khem Raj,
Quoted 5 lines · Khem Raj
there are other layers which you could look into and see if those recipe make sense to any of these layers please see
http://www.openembedded.org/wiki/LayerIndex
if not host them in your layer if u wish to maintain them and add your layer to above index
Ok. Will see whether any layer has the recipes that I wrote, if not I will host them separately.
Regards
Joshua
Signature · 3 lines
Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in
Quoted 1 line · Scott Garman
On 02/20/2012 06:03 AM, Joshua Immanuel wrote:
I ended up writing new
Quoted 8 lines
Quoted 3 lines
recipes for packages which does not exist in yocto. I think it will be useful for others. <snip> So, how do I contribute these new recipes?
Hi Joshua,
Quoted 8 lines
I'd put your layer up on a git repo somewhere (GitHub?) and make sure you have a note in your layer's README file that mentions that the layer is intended for use with the edison release.
Scott
Doesn't this project accept new community driven / supplied recipes?
Quoted 2 lines · Bob Cochran
Doesn't this project accept new community driven / supplied recipes?
Certainly it does. Layers are part of project.