From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] legal-info: add option to store manifest in rootfs
Date: Sat, 28 Apr 2018 17:15:12 +0200 [thread overview]
Message-ID: <20180428151512.GA2922@scaer> (raw)
In-Reply-To: <e8f0d25b-5d96-9b31-4203-4074f804680c@gmail.com>
Florian, All,
On 2018-04-27 14:39 -0700, Florian Fainelli spake thusly:
[--SNIP--]
> Let's drop this, I was not thinking this would go into such a lengthy
> discussion,
That's been just 4-5 mails so far. This is *far* from being a lengthy
discussion, especialy by Buildroot standards! ;-]
> I will keep the local hack I have with make legal-info in
> post-build.sh. Thanks a lot for your help Yann!
Alternatively, you can use a br2-external tree, with:
- Config.in is empty
- external.desc contains:
name: LEGAL_IN_TARGET
desc: Isntall legal-info in rootfs
- external.mk contains something like:
target-finalize: legal-info
TARGET_FINALIZE_LEGAL_INFO_DIR = $(TARGET_DIR)/usr/share/legal-info
define TARGET_FINALIZE_LEGAL_INFO
$(INSTALL) -D -m 0644 $(LEGAL_MANIFEST_CSV_TARGET) \
$(TARGET_FINALIZE_LEGAL_INFO_DIR)/$(notdir $(LEGAL_MANIFEST_CSV_TARGET))
mkdir -p $(TARGET_FINALIZE_LEGAL_INFO_DIR)/licenses
cp -a $(LICENSE_FILES_DIR_TARGET)/* \
$(TARGET_FINALIZE_LEGAL_INFO_DIR)/licenses/
endef
TARGET_FINALIZE_HOOKS += TARGET_FINALIZE_LEGAL_INFO
I've slightly tested that, and it seems to be working...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2018-04-28 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 19:32 [Buildroot] [PATCH RFC] legal-info: add option to store manifest in rootfs Yann E. MORIN
2018-04-26 21:47 ` Florian Fainelli
2018-04-27 13:46 ` Thomas Petazzoni
2018-04-27 16:14 ` Florian Fainelli
2018-04-27 16:31 ` Yann E. MORIN
2018-04-27 16:41 ` Florian Fainelli
2018-04-27 16:33 ` Luca Ceresoli
2018-04-27 16:45 ` Florian Fainelli
2018-04-27 20:02 ` Yann E. MORIN
2018-04-27 21:23 ` Luca Ceresoli
2018-04-27 21:39 ` Florian Fainelli
2018-04-28 10:20 ` Thomas Petazzoni
2018-04-30 19:16 ` Florian Fainelli
2018-04-28 15:15 ` Yann E. MORIN [this message]
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=20180428151512.GA2922@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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