From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: buildroot@buildroot.org
Cc: Herve Codina <herve.codina@bootlin.com>,
Andreas Naumann <anaumann@ultratronik.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Louis-Paul CORDIER <lpdev@cordier.org>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Adam Duskett <aduskett@gmail.com>
Subject: [Buildroot] [PATCH 0/3] core: fixup PPD paths (branch yem/ppd-fixup-paths)
Date: Sat, 8 Jan 2022 18:35:39 +0100 [thread overview]
Message-ID: <cover.1641663315.git.yann.morin.1998@free.fr> (raw)
Hello All!
This series builds upon previous good work from Andreas [0], Louis-Paul
[1], and Adam [2].
The second patch is the core of the change: rather than have multiple
hooks that each cater for different types of files (.py, .pc, .pri,
.cmake and so on), we jut do what we already do in relocate-sdk: we just
look for all text files that have a PPD prefix in them, and replace tht
with the cirrent package's PPD.
The third patch ensures that we can build reliable filrs lists, so that
files we tweak in the infra are not believed to be installed/modified by
the current package.
The first patch is just a little formatting cleanup.
[0] https://lore.kernel.org/buildroot/20200217212350.29750-21-anaumann@ultratronik.de/
[1] https://lore.kernel.org/buildroot/a339f273-33f3-f232-eac4-6e50427abf6d@cordier.org/
[2] https://lore.kernel.org/buildroot/20220106171720.12857-1-aduskett@gmail.com/
Regards,
Yann E. MORIN.
----------------------------------------------------------------
Yann E. MORIN (3):
core/pkg-utils: properly indent per-package-rsync
core/pkg-generic: fixup all PPD paths in a generic fashion
core/pkg-generic: apply post-prepare hooks before monitoring directories
package/pkg-generic.mk | 45 ++++++++++++++++++++++-----------------------
package/pkg-utils.mk | 4 ++--
2 files changed, 24 insertions(+), 25 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-01-08 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 17:35 Yann E. MORIN [this message]
2022-01-08 17:35 ` [Buildroot] [PATCH 1/3] core/pkg-utils: properly indent per-package-rsync Yann E. MORIN
2022-01-08 17:52 ` Peter Korsgaard
2022-01-08 17:35 ` [Buildroot] [PATCH 2/3] core/pkg-generic: fixup all PPD paths in a generic fashion Yann E. MORIN
2022-01-09 12:14 ` Herve Codina
2022-01-12 20:42 ` Arnout Vandecappelle
2022-01-13 21:58 ` Yann E. MORIN
2022-01-22 10:50 ` Yann E. MORIN
2022-01-08 17:35 ` [Buildroot] [PATCH 3/3] core/pkg-generic: apply post-prepare hooks before monitoring directories Yann E. MORIN
2022-01-09 12:11 ` Herve Codina
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=cover.1641663315.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=aduskett@gmail.com \
--cc=anaumann@ultratronik.de \
--cc=buildroot@buildroot.org \
--cc=herve.codina@bootlin.com \
--cc=lpdev@cordier.org \
--cc=thomas.petazzoni@bootlin.com \
/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