how can anyone maintain own yocto repository ?

[idata]

hello everyone,

What if i want to maintain my own yocto repository ? are there any specific steps that i have to perform ? how can i do that ?

how do I make packages that contain required dependencies to be yocto supported ? is there any utility or software or tool that can make yocto supported packages for us ?

thank you.

[Pedro_M_Intel]

Hello mailto:falak.desai@yahoo.com falak.desai@yahoo.com,

That is very interesting project, I have never supported/created a repo of any kind, nevertheless I found some links that could be of your interest, take a look at the following:

http://www.jumpnowtek.com/yocto/Managing-a-private-opkg-repository.html Managing a custom opkg repository

http://www.jumpnowtek.com/yocto/Using-your-build-workstation-as-a-remote-package-repository.html Using a Yocto build workstation as a remote opkg repository

https://groups.google.com/forum/# !topic/opkg-devel/yLg8vyxClow Google Groups

Another good suggestion would be to look for help of people that is actually experienced in maintaining a repo, like AlexT_Intel who has maintained a pretty good repo since the beginning of the Edison/Galileo boards.

Peter.

[AT9 · Accepted solution]

Yocto manual is a reference place to start with this, namely this section: http://www.yoctoproject.org/docs/1.7.2/dev-manual/dev-manual.html# using-runtime-package-management http://www.yoctoproject.org/docs/1.7.2/dev-manual/dev-manual.html# using-runtime-package-management

I've also described the process in my repo thread for Galileo, there's no real difference between Edison and Galileo in this regard (as both use Yocto). See here: