From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iXmds-0005NV-2p for distrokit@pengutronix.de; Thu, 21 Nov 2019 14:37:04 +0100 Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.89) (envelope-from ) id 1iXmdr-0002Pc-Qi for distrokit@pengutronix.de; Thu, 21 Nov 2019 14:37:03 +0100 Date: Thu, 21 Nov 2019 14:37:03 +0100 From: Michael Olbrich Message-ID: <20191121133703.5boamtmib4nmgyxm@pengutronix.de> References: <5050274.MR8Rb9Ot4Y@ada> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <5050274.MR8Rb9Ot4Y@ada> Subject: Re: [DistroKit] Multiple identical barebox source trees List-Id: DistroKit Mailinglist List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: distrokit-bounces@pengutronix.de Sender: "DistroKit" To: distrokit@pengutronix.de Hi, On Tue, Nov 19, 2019 at 10:33:42AM +0100, Alexander Dahl wrote: > today I had a look at how the different barebox packages are built, after > loosely following the Git history on those. Main reason is I want to follow a > similar approach for U-Boot. Revision I'm looking at is recent master, aka > 2018-02-espressobin-v3-183-ga4f6ef2. > > There's a rather new package barebox-common and all barebox-* packages share > the same version and patch stack. Also: barebox-* packages are built out of > tree (OOT). So I somehow expected in platform-v7a/build-target there would be > one extracted source tree, all patches applied on top, and each barebox-* > package built oot from that one source tree. However that's not the case, I > have found the following folders all containing the same (clean) source tree: > > barebox-am335x-2019.11.0 > barebox-am335x-mlo-2019.11.0 > barebox-common-2019.11.0 > barebox-mx6-2019.11.0 > barebox-rpi2-2019.11.0 > barebox-vexpress-2019.11.0 > > Is it possible with ptxdist to also share the source tree? That could save > some time for unpacking and patching, right? It's not really possible in a sane way. The Problem is, how would 'clean' for one of the barebox packages work? It's not really clean, when the source is not deleted. Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ DistroKit mailing list DistroKit@pengutronix.de