From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: =?iso-8859-15?q?J=FCrgen_Beisert?= Date: Wed, 8 Jan 2014 08:59:43 +0100 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201401080859.43988.jbe@pengutronix.de> Subject: Re: [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: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: "Olbrich, Michael" Hi Jon, On Wednesday 08 January 2014 03:32:41 Jon Ringle wrote: > 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 we= ll > 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 rep= os > 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 wh= at > others are doing in this regard. Do you want to use this BSP only by your own, or is it intended to provide = it = to other developers who use it as a base for their own work? In the latter case I would "release" the various components and create arch= ives = of it. And these archives can simply be part of the (finally) released BSP = you = provide to other developers (in contrast to the downloadable archives PTXdi= st = uses for the remaining packages like Busybox, Qt and so on). If you still want to use git repositories for the external components we sh= ould = wait for Michael, because he can explain how to use the PTXdist feature whi= ch = deals with such repositories. Regards, jbe -- = Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0| Juergen Beisert =A0 =A0 =A0 =A0 =A0 =A0 | Linux Solutions for Science and Industry =A0 =A0 =A0| http://www.pengutroni= x.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de