public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
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: Fri, 19 Mar 2004 01:45:00 -0000	[thread overview]
Message-ID: <405A509E.9050406@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.

Okay, I'm being noisy here, but now on rereading/rethinking, I think I'm 
wrong on the above reasoning.

However there is still an issue.... right now we allow any works based on 
eCos to be distributed with the GPL exception clause. This permits people 
to distribute unlinked or partially linked objects, e.g. libtarget.a etc. 
with no further restrictions than if they distributed other binaries.

The RTEMS license only permits executable applications to be distributed 
with the exception, so if someone distributes libtarget.a, then it becomes 
fully GPL'd, and so their whole application would become GPL'd. This is an 
undesirable new restriction.

So yes there is still a problem and I'll send that to ecos-discuss.

Jifl
-- 
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

      parent reply	other threads:[~2004-03-19  1:45 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
2004-03-19  1:34       ` Jonathan Larmour
2004-03-19  1:45       ` Jonathan Larmour [this message]

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=405A509E.9050406@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).