[meta-freescale] A source control for custom recipes
Bob Cochran
yocto at mindchasers.com
Sun Dec 16 19:14:38 PST 2018
On 12/12/18 5:35 PM, John Matt wrote:
> Hi Bob,
>
> Thanks for the response.
>
> I am wondering if people use repo tool or gitsubmodules? Currently, I
> am debating if I need to copy the YOCTO repo to my local git (we have
> an internal git), or use the YOCTO repo externally, and only manage my
> recipes in my internal git in my organization?
We set up a poky folder on each build machine and then clone all the
Yocto related repos under it (e.g., meta-openembedded, meta-raspberrypi,
etc.).
We use our own Python script to manage all our the repos that we work
with (e..g, run multiple git pull or checkout <branch> / <commit>). It
was a pretty simple thing to write (still a work in progress).
Repo (by Google?) seemed a lot heavier than what we needed, so writing
our own script gave us the control we needed & we could understand
everything it does.
Bob
>
>
> Regards,
> Janarbek.
>
> On Tue, Dec 11, 2018 at 8:28 PM Bob Cochran <yocto at mindchasers.com
> <mailto:yocto at mindchasers.com>> wrote:
>
> On 12/11/18 5:39 PM, John Matt wrote:
>> Hi All,
>>
>> I am newbie, and I am wondering what is the accepted way of using
>> git (source control) for custom recipes in Yocto?
>>
>> My recipes are very custom that now one except my team needs
>> them, and I am wondering what is the suggested way of managing
>> custom recipes? We are using Yocto .2.5.
>>
>> Thanks in advance,
>> J.
>>
> Hi John,
>
> We have lots of internal recipes for our own projects and plenty
> of customizations (e.g., bbappend). We manage these by
> maintaining our own layer and keeping a bare repo of the layer on
> a shared drive that everyone / all machines pull from and push to.
>
> Bob
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20181216/e2d44447/attachment.html>
More information about the meta-freescale
mailing list