From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: =?iso-8859-15?q?J=FCrgen_Beisert?= Date: Thu, 9 Jan 2014 09:10:46 +0100 References: <201401080859.43988.jbe@pengutronix.de> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201401090910.46265.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 15:14:26 Jon Ringle wrote: > On Wed, Jan 8, 2014 at 2:59 AM, J=FCrgen Beisert wro= te: > > 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 > > archives 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 PTXdist uses for the remaining packages like Busy= box, > > Qt and so on). = > > > Yes, this will be for other developers to base their work off of. > > So, what exactly would be included in the "release" BSP? > platform/sysroot-*/ and platform/root*/ ?? No. These directories exist at buildtime only and will be recreated and fil= led = up at each PTXdist run. Their content depends on the selected toolchain and = package selection. You should keep this behaviour for the user of the BSP. Maybe I read your first question wrong: You have some development made and = the = results are part of a few external git repositories, haven't you? Why not tar them (not the whole repository, just a released variant: git = archive --format=3Dtar ...) and include the archive in the BSP? The = corresponding rule file uses a local URL pointing to this archive and you a= re = done. > > If you still want to use git repositories for the external components we > > should wait for Michael, because he can explain how to use the PTXdist > > feature which deals with such repositories. > > > Yes, I'd like to understand better ptxdist features to support externat > components maintained by our own git repos :) But this can work only, if everyone using your BSP has access to these = repositories. Regards, Juergen -- = 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