From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [RFC PATCH] doc: Add section on creating new layers
Date: Tue, 03 Sep 2019 14:22:04 +0200 [thread overview]
Message-ID: <2446051.fMRPiYAuoM@ada> (raw)
In-Reply-To: <20190903120017.uxirotubv2uiwgjp@pengutronix.de>
Hello Roland,
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:
> > After discussing these topics in IRC, it seemed reasonable to add some
> > explanation on how to create a new layer from scratch.
>
> \o/ someone else did a task on my overlong todo list :D
Yes, and I just saw you already wrote a piece on that topic, but on your
website, not in ptxdist documentation:
https://pengutronix.de/en/blog/2019-06-18-DistroKitLayer.html
o.O
> > +
> > +Creating a new Layer
> > +~~~~~~~~~~~~~~~~~~~~
> > +
> > +Adding new layers on top of an already existing BSP is easy:
> > +
> > +#. Create an empty folder, e.g. next to the existing BSP.
> > +#. The lower layer is just a folder named ``base`` (see layers_ above).
> > You + may do one of the following (or something else you consider
> > convenient): +
> > + - Create a symbolic link ``base`` to an outside laying BSP folder. For
> > + an easy start, you can try this method with DistroKit_ for example:
> > + ``$ ln -s ../DistroKit base``
>
> We have done that too sometimes in the past, but if the config files in
> the base layer are not in the right versions, the MD5 sum in the config
> diffs in the inherited layer will not match. I think this should be
> mentioned here.
Sorry, I do not understand. :-/
> > + - Use a Git submodule with a BSP in a folder ``base``.
> > + - Copy over your whole existing BSP to a new subfolder ``base``.
>
> Subtree merges are another possibility, although I've never done one.
Same here.
> > +
> > +#. 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. ;-)
> > +
> > +#. Use ``ptxdist menu`` like usual.
>
> menuconfig? platformconfig?
You reach both from `p menu` … but I don't mind changing this.
> > +#. Put your new layer into Git and add configs and delta configs to it.
>
> nit: s/Git/SCM/, or something like that
Yes.
So you already wrote on that topic. I wouldn't mind if you take my patch as
base for your own additions. O:-)
Greets
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-09-03 12: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 [this message]
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
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=2446051.fMRPiYAuoM@ada \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
--cc=rhi@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