From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 04 Mar 2022 16:34:35 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nQ9wx-0006DZ-O7 for lore@lore.pengutronix.de; Fri, 04 Mar 2022 16:34:35 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nQ9ww-0007df-GM; Fri, 04 Mar 2022 16:34:34 +0100 Received: from ptx.hi.pengutronix.de ([2001:67c:670:100:1d::c0]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nQ9wh-0007dV-RH; Fri, 04 Mar 2022 16:34:19 +0100 Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.92) (envelope-from ) id 1nQ9wh-0003Ff-AJ; Fri, 04 Mar 2022 16:34:19 +0100 Date: Fri, 4 Mar 2022 16:34:19 +0100 From: Michael Olbrich To: Christian Melki Message-ID: <20220304153419.GS12709@pengutronix.de> Mail-Followup-To: Christian Melki , ptxdist@pengutronix.de References: <20220303134028.GN12709@pengutronix.de> <7ee003fb-e6c3-34d7-d9e2-d29279369b0c@t2data.com> <9e421142-d037-6b62-79c4-2a7a9a09d120@benfm.de> <00ae8995-135e-dc67-737e-4c7d6ec3e08a@t2data.com> <20220303201138.GB26895@falbala.internal.home.lespocky.de> <20220303203533.GC26895@falbala.internal.home.lespocky.de> <1640a3d2-3882-2b3f-e926-155a94099776@t2data.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1640a3d2-3882-2b3f-e926-155a94099776@t2data.com> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-IRC: #ptxdist @freenode X-Accept-Language: de,en X-Accept-Content-Type: text/plain X-Uptime: 16:23:58 up 84 days, 9 min, 82 users, load average: 0.11, 0.14, 0.17 User-Agent: Mutt/1.10.1 (2018-07-13) Subject: Re: [ptxdist] Patch series for package per project? X-BeenThere: ptxdist@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Cc: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ptxdist" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: ptxdist-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false On Fri, Mar 04, 2022 at 04:16:23PM +0100, Christian Melki wrote: > On 3/4/22 9:10 AM, Michael Olbrich wrote: > > On Thu, Mar 03, 2022 at 09:35:36PM +0100, Alexander Dahl wrote: > > > On Thu, Mar 03, 2022 at 09:11:39PM +0100, Alexander Dahl wrote: > > > > On Thu, Mar 03, 2022 at 08:37:45PM +0100, Christian Melki wrote: > > > > > On 3/3/22 18:07, Felix Mellmann wrote: > > > > > > On 03.03.22 15:22, Christian Melki wrote: > > > > > > > Just one barebox version, but for different archs, with different > > > > > > > patchsets. I'd like the patches to live in the same place as they've > > > > > > > always done, i.e. under patches/package/... > > > > > > > But patches/package/series.$platform or similar does not seem to work? > > > > > > > > > > > > > Would it be an option to put the patches below each of the platformdirs? > > > > > > > > > > > > I ran into a similiar situation when starting to migrate to a different > > > > > > CPU platform. After a couple of years putting serveral "platformconfig" > > > > > > files within the same directory as "ptxconfig" I'm now using separate > > > > > > subdirs for each platform where separate sets of platform dependent > > > > > > patches are lying. > > > > That would be my first suggestion as well. > > > > Hm. My ptxdist setup seems to point to the bin/patches before > projects/projectname/patches directory if i print the PATH_PATCHES variable. > Default afaik? > > And it doesn't continue if patches are available in some other directory. > So if I have generic patches in bin/patches, or if I want them overridden it > won't work? > > I must have missed something? How is this supposed to work? So I'm not sure, what you mean by bin/patches and projects/projectname/patches, so I'll explain the search order in general. I'll refer to the Toplevel directory of the BSP as 'bsp/'. That's the directory you're in when ptxdist is called. Then there is the directory where your platformconfig is located. That's typically 'bsp/configs/platform-foo/'. And of course there is PTXdist itself. I'll use 'ptxdist/' for that. When ptxdist searches for patches then it goes through a list of directories and picks the first one that's found. For historical reasons the order looks like this (for package bar-1.0): bsp/patches/bar-1.0/ bsp/configs/platform-foo/patches/bar-1.0/ And if there are any layers: base/bsp/patches/bar-1.0/ base/bsp/configs/platform-foo/patches/bar-1.0/ Repeat this by adding another base/ in each loop. And finally: ptxdist/patches/bar-1.0/ So if you want a default patch stack for multiple platforms, then put the default in base/bsp/patches/bar-1.0/. Then you can overwrite it in on platform with bsp/configs/platform-foo/patches/bar-1.0/. 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 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de