From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baruch Siach Date: Tue, 16 Aug 2016 17:29:50 +0300 Subject: [Buildroot] [PATCH 1/1] package/simh: new package In-Reply-To: <9ba51c53-ddb3-8a59-a3b0-9ba8e3e52f3e@gmail.com> References: <1471297357-11637-1-git-send-email-lothar.felten@gmail.com> <20160816035044.GB3368@tarshish> <9ba51c53-ddb3-8a59-a3b0-9ba8e3e52f3e@gmail.com> Message-ID: <20160816142950.GH3368@tarshish> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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 _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 _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 -