From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/simh: new package
Date: Tue, 16 Aug 2016 17:29:50 +0300 [thread overview]
Message-ID: <20160816142950.GH3368@tarshish> (raw)
In-Reply-To: <9ba51c53-ddb3-8a59-a3b0-9ba8e3e52f3e@gmail.com>
Hi Lothar,
As Yann marked this patch as rejected, this discussion is moot. But I'll
respond below for future reference.
On Tue, Aug 16, 2016 at 10:31:10AM +0200, Lothar Felten wrote:
> On 16.08.2016 05:50, Baruch Siach wrote:
> > Looking into a random source file like sim_imd.c, the license seems to be
> > MIT. See https://opensource.org/licenses/MIT.
>
> Most files have a MIT-license/disclaimer, a few files reference GNU GPL
> (Intel-Systems/common/i8088.c), at least one file is paritally zlib/libpng
> license (sim_video.c, line 102), one file is "licensed under the standard
> SimH license" (PDP11/pdp11_kmc.c), which seems to be MIT.
In this case <PKG>_LICENSE should list all these licenses.
> There's a Word .doc file doc/simh.doc that states:
>
> COPYRIGHT NOTICE: The following copyright notice applies to the SIMH source,
> binary, and documentation (an then: MIT license)
>
> An older PDF version is online:
> http://simh.trailing-edge.com/pdf/simh_doc.pdf
>
> Should I point to the simh.doc file?
I don't think so. Not sure how our legal info infra handles binary document
formats. Instead you may put source files that contain respective licenses
text in <PKG>_LICENSE_FILES.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-08-16 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 21:42 [Buildroot] [PATCH 1/1] package/simh: new package Lothar Felten
2016-08-16 3:50 ` Baruch Siach
2016-08-16 8:31 ` Lothar Felten
2016-08-16 14:29 ` Baruch Siach [this message]
2016-08-16 19:42 ` Yann E. MORIN
2016-08-18 19:27 ` Thomas Petazzoni
2016-08-18 19:53 ` Yann E. MORIN
2016-08-16 10:52 ` Yann E. MORIN
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=20160816142950.GH3368@tarshish \
--to=baruch@tkos.co.il \
--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.