From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Including legal-info manifest into rootfs?
Date: Thu, 26 Apr 2018 21:35:34 +0200 [thread overview]
Message-ID: <20180426193534.GA2471@scaer> (raw)
In-Reply-To: <6235a2ee-dc86-a18f-2278-5915bb1027ca@gmail.com>
Florian, All,
On 2018-04-26 09:55 -0700, Florian Fainelli spake thusly:
> I find myself in need of including the legal-info manifest into the
> rootfs, there does not appear to be a package that would include that,
> but that would seem like a natural approach to doing this.
>
> Right now this is done as a step in post-build.sh, but this is less than
> ideal because it still makes it environment specific.
>
> Has anybody done that before?
Now, yes: https://patchwork.ozlabs.org/patch/905327/ ;-)
Note: I find it a bit haskish still, so thorough testing would be needed. ;-)
Especially, I haven't tested how it works with an initralfs or initrd
linked into the kernel...
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-26 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 16:55 [Buildroot] Including legal-info manifest into rootfs? Florian Fainelli
2018-04-26 19:35 ` 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=20180426193534.GA2471@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.