From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH] doc: Add section on creating new layers
Date: Tue, 3 Sep 2019 16:22:55 +0200 [thread overview]
Message-ID: <20190903142255.hxisijxauvyb46b7@pengutronix.de> (raw)
In-Reply-To: <1795891.LWLpe0IM0S@ada>
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
next prev parent reply other threads:[~2019-09-03 14:22 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
2019-09-03 14:22 ` Michael Olbrich [this message]
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=20190903142255.hxisijxauvyb46b7@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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