From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 26 Mar 2024 07:59:23 +0100 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1rp0mJ-004pUe-0d for lore@lore.pengutronix.de; Tue, 26 Mar 2024 07:59:23 +0100 Received: from localhost ([127.0.0.1] helo=metis.whiteo.stw.pengutronix.de) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1rp0mI-0005Tq-VA; Tue, 26 Mar 2024 07:59:22 +0100 Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rp0lx-0005TO-Ex; Tue, 26 Mar 2024 07:59:01 +0100 Received: from [2a0a:edc0:2:b01:1d::c5] (helo=pty.whiteo.stw.pengutronix.de) by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rp0lx-008Z8z-0I; Tue, 26 Mar 2024 07:59:01 +0100 Received: from mol by pty.whiteo.stw.pengutronix.de with local (Exim 4.96) (envelope-from ) id 1rp0lw-00Hafs-2z; Tue, 26 Mar 2024 07:59:00 +0100 Date: Tue, 26 Mar 2024 07:59:00 +0100 From: Michael Olbrich To: Mircea Ciocan Message-ID: Mail-Followup-To: Mircea Ciocan , ptxdist References: <1989187181.547813.1710251224129.JavaMail.zimbra@ppc-ag.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1989187181.547813.1710251224129.JavaMail.zimbra@ppc-ag.de> X-Sent-From: Pengutronix Hildesheim X-URL: http://www.pengutronix.de/ X-Accept-Language: de,en X-Accept-Content-Type: text/plain Subject: Re: [ptxdist] What can be actually set in a collection 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 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.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false Hi, On Tue, Mar 12, 2024 at 02:47:04PM +0100, Mircea Ciocan wrote: > in an attempt to consolidate multiple similar platforms under one > ptxconfig + individual collection configs we are not sure if in the > collection only individual software packages can be set that have been > already marked with in the root ptxconfig, or other things, like > variables containing a string or different build options for a specific > package can be put in a collection. Collections only work to get a subset of packages. They cannot be used for other options. > If these things can't be stored in a collection, can be stored somewhere > else so they can be merged with the global ptxdist when a specific > configuration is selected ? If you need more than what collections allow, then I suggest you use layers. A layer allows you to store what is basically a diff for the base ptxconfig. You can do the same thing for other configs, such as the platformconfig or a kernelconfig. It can have a separate projectroot/ to overwrite things from the base BSP. You can customize just about everything in the BSP but still keep the common parts in one place. > Can/will the already define variable be overridden ? Is there any related documentation ? Collections are not really documented. They are rarely used because of the limitations you noticed. Layers are documented[1], but I'm use that could be better :-). Feel free to ask questions here if anything is unclear. Michael [1] https://www.ptxdist.org/doc/dev_layers_in_ptxdist.html -- 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 |