[ptxdist] git ptxdist best practices

[Jon Ringle <jon@ringle.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1087 bytes --]

I'm looking for some best practices ideas as it relates to using ptxdist to
build a complete system that pulls from various git repos.

I have a clone Linux git repo that has local commits specific to our
embedded hardware.
I build an initramfs filesystem with ptxdist that gets embedded within the
Linux kernel image.
I build a rootfs with ptxdist for the real rootfs
I also have a couple of libs and apps that have their own git repos as well
that I'm getting ptxdist to build as well.

I'm now at the point where I now need to make this available to other
developers and also get setup for a build bot to build (bamboo).

My initial thought is to create a git repo that holds the ptxconfig files
and local rules/, and then configure the rules to somehow get the git repos
by tag for building (as it seems that there is some sort of support for
this in scripts/lib/ptxd_make_get.sh)... but I don't quite understand how
to integrate this in my rules/*.make file.

Perhaps there is a better way of doing this. I'd be interested to hear what
others are doing in this regard.

Thanks,
Jon

[-- Attachment #1.2: Type: text/html, Size: 1247 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de