From: Michael Olbrich <m.olbrich@pengutronix.de>
To: distrokit@pengutronix.de
Subject: Re: [DistroKit] Multiple identical barebox source trees
Date: Thu, 21 Nov 2019 14:37:03 +0100 [thread overview]
Message-ID: <20191121133703.5boamtmib4nmgyxm@pengutronix.de> (raw)
In-Reply-To: <5050274.MR8Rb9Ot4Y@ada>
Hi,
On Tue, Nov 19, 2019 at 10:33:42AM +0100, Alexander Dahl wrote:
> today I had a look at how the different barebox packages are built, after
> loosely following the Git history on those. Main reason is I want to follow a
> similar approach for U-Boot. Revision I'm looking at is recent master, aka
> 2018-02-espressobin-v3-183-ga4f6ef2.
>
> There's a rather new package barebox-common and all barebox-* packages share
> the same version and patch stack. Also: barebox-* packages are built out of
> tree (OOT). So I somehow expected in platform-v7a/build-target there would be
> one extracted source tree, all patches applied on top, and each barebox-*
> package built oot from that one source tree. However that's not the case, I
> have found the following folders all containing the same (clean) source tree:
>
> barebox-am335x-2019.11.0
> barebox-am335x-mlo-2019.11.0
> barebox-common-2019.11.0
> barebox-mx6-2019.11.0
> barebox-rpi2-2019.11.0
> barebox-vexpress-2019.11.0
>
> Is it possible with ptxdist to also share the source tree? That could save
> some time for unpacking and patching, right?
It's not really possible in a sane way. The Problem is, how would 'clean'
for one of the barebox packages work? It's not really clean, when the
source is not deleted.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2019-11-21 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 9:33 Alexander Dahl
2019-11-21 13:37 ` Michael Olbrich [this message]
2019-11-22 7:25 ` Alexander Dahl
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=20191121133703.5boamtmib4nmgyxm@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=distrokit@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