From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.thorsis.com ([92.198.35.195]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1i59AS-0007za-Vt for ptxdist@pengutronix.de; Tue, 03 Sep 2019 15:48:21 +0200 Received: from localhost (localhost [127.0.0.1]) by mail.thorsis.com (Postfix) with ESMTP id 7BBD147D9 for ; Tue, 3 Sep 2019 15:49:39 +0200 (CEST) Received: from mail.thorsis.com ([127.0.0.1]) by localhost (mail.thorsis.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krhB4EcDtRMR for ; Tue, 3 Sep 2019 15:49:39 +0200 (CEST) From: Alexander Dahl Date: Tue, 03 Sep 2019 15:48:17 +0200 Message-ID: <1795891.LWLpe0IM0S@ada> In-Reply-To: <20190903130808.vg6cxfnhx23kh5uw@pengutronix.de> References: <20190903115025.5007-1-ada@thorsis.com> <2446051.fMRPiYAuoM@ada> <20190903130808.vg6cxfnhx23kh5uw@pengutronix.de> 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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de Hei hei, Am Dienstag, 3. September 2019, 15:08:08 CEST schrieb Michael Olbrich: > On Tue, Sep 03, 2019 at 02:22:04PM +0200, Alexander Dahl wrote: > > Am Dienstag, 3. September 2019, 14:00:17 CEST schrieb Roland Hieber: > > > On Tue, Sep 03, 2019 at 01:50:25PM +0200, Alexander Dahl wrote: > > > > + > > > > +#. If needed select **ptxconfig** and/or **platformconfig** after > > > > copying > > > > + that file from the lower layer to your new layer: > > > > + > > > > +.. code-block:: text > > > > + > > > > + $ mkdir -p configs/platform-v7a > > > > + $ cp base/configs/platform-v7a/platformconfig > > > > configs/platform-v7a/ > > > > + $ ptxdist platform configs/platform-v7a/platformconfig > > > > > > I think you should be able to select the config from base/ directly > > > without copying them? mol? > > > > I did not try that. What is possible to select would be indeed an > > interesting piece in the docs! That question came up multiple times in > > IRC in the last days. ;-) > > 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? > 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. > 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? Greets Alex _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de