From: Bill Pringlemeir <bpringle@sympatico.ca>
To: Thierry Moreau <thierry.moreau@connotech.com>
Cc: Per-Arnold.Blaasmo@atmel.com, crossgcc@sourceware.org
Subject: Re: License text in finished built toolchain?
Date: Fri, 20 Apr 2012 16:02:00 -0000 [thread overview]
Message-ID: <BLU0-SMTP71A629F719E952750AB712B8220@phx.gbl> (raw)
In-Reply-To: <4F916E4A.3030708@connotech.com> (Thierry Moreau's message of "Fri, 20 Apr 2012 10:10:18 -0400")
Per Arnold Blaasmo wrote:
>> Do we need to have the license files in the finished build tree?
>> Should crosstool-ng copy those in to the finished tree?
>> What about crosstool-ng's license?
>> Do we need to add that to the finished built toolchain?
>> Do anyone have any thought on this?
On 20 Apr 2012, thierry.moreau@connotech.com wrote:
> I don' se the point for crossgcc developers/maintainers to delve into
> these issues for you. Their time is best used elsewhere.
I don't think it is a bad idea for crosstool-ng to copy a licence
file(s) to the finished tree. I don't see one for anything but 'ltrace'
in my trees in '<tuple>/debug-root/usr/share/doc/ltrace/COPYING'. CT-NG
is already putting a compressed build log there. There is no 'choice'
of licence. It is GPL/LGPL/GCC and having those files present in the
finished tree makes sense doesn't it?
I don't think it is a pressing matter, but I wouldn't say that Per
Arnold's suggestion was *not* worth any attention. Actually, I am
surprised that the GCC, etc build files haven't installed a licence file
somewhere... but maybe I missed something in the finished tree.
Debian/Ubuntu provide on in /usr/share/doc/gcc-4.4-base/copyright. I
guess getting the constituent package licences right for an aggregate
license might be an issue; if it is a simple 'cp' how could it not be
worth the time?
fwiw,
Bill Pringlemeir.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-04-20 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 8:16 Per Arnold Blaasmo
2012-04-20 14:03 ` Thierry Moreau
2012-04-20 16:02 ` Bill Pringlemeir [this message]
2012-04-20 18:28 ` Michael Eager
2012-04-21 22:27 ` Oron Peled
2012-04-22 0:01 ` Michael Eager
2012-04-23 17:19 ` Yann E. MORIN
2012-04-23 21:46 ` Michael Hope
2012-04-23 22:21 ` Oron Peled
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=BLU0-SMTP71A629F719E952750AB712B8220@phx.gbl \
--to=bpringle@sympatico.ca \
--cc=Per-Arnold.Blaasmo@atmel.com \
--cc=crossgcc@sourceware.org \
--cc=thierry.moreau@connotech.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).