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 1i59hw-00046E-1z for ptxdist@pengutronix.de; Tue, 03 Sep 2019 16:22:56 +0200 Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.89) (envelope-from ) id 1i59hv-0007Bq-Q4 for ptxdist@pengutronix.de; Tue, 03 Sep 2019 16:22:55 +0200 Date: Tue, 3 Sep 2019 16:22:55 +0200 From: Michael Olbrich Message-ID: <20190903142255.hxisijxauvyb46b7@pengutronix.de> References: <20190903115025.5007-1-ada@thorsis.com> <2446051.fMRPiYAuoM@ada> <20190903130808.vg6cxfnhx23kh5uw@pengutronix.de> <1795891.LWLpe0IM0S@ada> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1795891.LWLpe0IM0S@ada> Subject: Re: [ptxdist] [RFC PATCH] doc: Add section on creating new layers List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de On Tue, Sep 03, 2019 at 03:48:17PM +0200, Alexander Dahl wrote: > Am Dienstag, 3. September 2019, 15:08:08 CEST schrieb Michael Olbrich: > > If there is just on platform, then ptxdist will just use that on if no > > selected_platformconfig exists. This is especially useful with layers, > > because it will then just pick the config from the first layer that has > > one. > > So this is not different to ptxdist behaviour without layers. Maybe DistroKit > is no good example, because it contains more than one platform and you must > select one to get going? Correct. You need to select one (or run ptxdist with --platformconfig=...). Once ptxdist has crated a platformconfig for the new layer, you need to select that one. PTXdist will complain if you forget this step. > > This means, that you can start with just the base link. Then change > > something with 'ptxdist platformconfig'. PTXdist will create the > > platformconfig in your new layer and use it automatically. > > > > The same works for the ptxconfig as well. > > > > Note: ptxdist will delete the config if it is identical to the layer below. > > I think this is very convenient. This makes creating a new layer even easier, > at least for BSPs with exactly one ptxconfig and exactly one platformconfig. That's the most common use case, so I made sure that this is easy. > > It does not touch the selected_* links you might need to change those if it > > happens. > > So the question remains. If there is more than one platform or config, where > should it be selected best and how? Only selections in the current layer are used. Anything else is ignored. And PTXdist enforces that the selected config is from the top layer (if the config exists there) or the next layer that contains it. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de