From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH] doc: Add section on creating new layers
Date: Tue, 03 Sep 2019 15:48:17 +0200 [thread overview]
Message-ID: <1795891.LWLpe0IM0S@ada> (raw)
In-Reply-To: <20190903130808.vg6cxfnhx23kh5uw@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
next prev parent reply other threads:[~2019-09-03 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 11:50 Alexander Dahl
2019-09-03 12:00 ` Roland Hieber
2019-09-03 12:22 ` Alexander Dahl
2019-09-03 13:08 ` Michael Olbrich
2019-09-03 13:38 ` Roland Hieber
2019-09-03 14:12 ` Michael Olbrich
2019-09-04 10:30 ` Roland Hieber
2019-09-04 12:55 ` Roland Hieber
2019-09-03 13:48 ` Alexander Dahl [this message]
2019-09-03 14:22 ` Michael Olbrich
2019-09-03 18:49 ` Alexander Dahl
2019-09-04 5:37 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1795891.LWLpe0IM0S@ada \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox