From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] legal info: saving of external toolchain
Date: Thu, 10 Oct 2013 22:37:21 +0200 [thread overview]
Message-ID: <52571001.5000508@lucaceresoli.net> (raw)
In-Reply-To: <CAAXf6LXAP+nsmMm7fp0_xvzLNT8cAYof4DECUYhpSs1RzE3Zeg@mail.gmail.com>
Hi Thomas,
Thomas De Schampheleire wrote:
> Hi Luca, all,
>
> The legal info infrastructure currently does not do anything for the
> toolchain, for 'technical reasons'. I can't recall what these
> technical reasons where. At least for external toolchains I don't see
> a big problem to copy the toolchain also in the sources/ subdirectory.
> The developer then still has the obligation to also provide the
> sources that accompany this binary distribution of the toolchain
> (which is impossible for buildroot to do), but at least the binary
> version is already taken care of.
Some stuff is better than no stuff. :)
>
> In fact, the legal-info target already calls toolchain-legal-info, but
> it does not do anything really.
>
> What do you think about implementing this for external toolchains (at
> least)? The fact that the toolchain is now using the package
> infrastructure probably makes that a tad easier.
Indeed it should be quite straightforward. It the toolchain is
downloaded, then the tarball may just be copied (or hardlinked).
Otherwise we simply have to tar the toolchain directory.
--
Luca
next prev parent reply other threads:[~2013-10-10 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 14:51 [Buildroot] legal info: saving of external toolchain Thomas De Schampheleire
2013-10-10 20:37 ` Luca Ceresoli [this message]
2013-10-10 21:04 ` Thomas Petazzoni
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=52571001.5000508@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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