From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: [ECOS] Re: RE : [ECOS] Licence consideratios.
Date: Thu, 18 Mar 2004 15:09:00 -0000 [thread overview]
Message-ID: <4059BBBB.6080809@eCosCentric.com> (raw)
In-Reply-To: <4059BB7E.9020100@eCosCentric.com>
Jonathan Larmour wrote:
> This is the license in question. http://www.rtems.com/license/LICENSE
>
> IANAL of course, but I believe it is incompatible: "[...] linking other
> files with RTEMS objects to produce an executable application, does not
> by itself cause the resulting executable application to be covered
> by the GNU General Public License."
>
> This will be linked with non-RTEMS objects. Therefore the full GPL would
> apply, therefore it is not acceptable, sorry. We can put it up in our
> contributions section, but not include it in the main source base.
Sorry, I didn't finish like intended.... I just want to check, do people
agree with my interpretation?
Jifl
> Andrew Lunn wrote:
>
>>> In fact, licence terms were not included into the files I downloaded.
>>> I have contacted the original contributor that said to me the package
>>> was released under "RTEMs licence".
>>> Regarding the name of four licences, I assumed it was "Primary licence".
>>>
>>> Then I have included RTEMs "Primary licence" terms into files and
>>> submited those files to the original contributor for agreement.
>>> He gave me this agreement.
>>>
>>> But I can't switch to eCos licence as, I think, all contributors should
>>> give their agreement.
>>
>>
>>
>> True.
>>
>>> Is this a problem to include files into eCos distribution?
>>
>>
>>
>> Now we know which license we are talking about, we can read it and see
>> if its compatible.
>> Andrew
>>
>
>
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
>>>>> Visit us in booth 2527 at the Embedded Systems Conference 2004 <<<<<
March 30 - April 1, San Francisco http://www.esconline.com/electronicaUSA/
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next prev parent reply other threads:[~2004-03-18 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040316145729.GB31390@lunn.ch>
[not found] ` <000301c40b6b$b0d064b0$7407a8c0@figuier>
[not found] ` <20040316153617.GC31390@lunn.ch>
2004-03-18 15:08 ` Jonathan Larmour
2004-03-18 15:09 ` Jonathan Larmour [this message]
2004-03-19 1:34 ` Jonathan Larmour
2004-03-19 1:45 ` Jonathan Larmour
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=4059BBBB.6080809@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
/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).