From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-lb0-x22a.google.com ([2a00:1450:4010:c04::22a]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W0iwp-0000Eo-H6 for ptxdist@pengutronix.de; Wed, 08 Jan 2014 03:32:48 +0100 Received: by mail-lb0-f170.google.com with SMTP id c11so885336lbj.15 for ; Tue, 07 Jan 2014 18:32:41 -0800 (PST) MIME-Version: 1.0 Date: Tue, 7 Jan 2014 21:32:41 -0500 Message-ID: From: Jon Ringle Subject: [ptxdist] git ptxdist best practices Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1600704527==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de --===============1600704527== Content-Type: multipart/alternative; boundary=001a11c3560c9a061104ef6c4e05 --001a11c3560c9a061104ef6c4e05 Content-Type: text/plain; charset=ISO-8859-1 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 --001a11c3560c9a061104ef6c4e05 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'm looking for some bes= t 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 r= epo 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 roo= tfs
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 ptxco= nfig files and local rules/, and then configure the rules to somehow get th= e git repos by tag for building (as it seems that there is some sort of sup= port for this in scripts/lib/ptxd_make_get.sh)... but I don't quite und= erstand how to integrate this in my rules/*.make file.

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

Thanks,
Jon
--001a11c3560c9a061104ef6c4e05-- --===============1600704527== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============1600704527==--