public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: guangbutun@hotmail.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ecos licensing FAQ queries
Date: Fri, 01 Mar 2002 10:32:00 -0000	[thread overview]
Message-ID: <200203011808.g21I8XV11052@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <LAW2-F179rQmFsZkgTZ000199b1@hotmail.com> (guangbutun@hotmail.com)

>>>>> "Butun" == Butun Guang <guangbutun@hotmail.com> writes:

    Butun> How do you define a LARGER WORK. It's obvious that it
    Butun> covers the situation someone develops a product on top of
    Butun> ecos. How about someone develops an operating system, can
    Butun> he benefit from ecos packeges, i.g., just includes or
    Butun> modifies one package (like just one device driver code),
    Butun> and deliver within their product?

Note: I am not a company lawyer so this response should be treated as
my personal opinion rather than an official position.

The RHEPL applies to the eCos source files individually, not to eCos
in its entirety. If you use one or more source files from any eCos
package, for example a device driver, with your application then the
terms of the RHEPL apply to that use. It does not matter whether or
not your application is a typical eCos application, built on top of
some eCos HAL and other packages.

Bart

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      reply	other threads:[~2002-03-01 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 14:58 Butun Guang
2002-03-01 10:32 ` Bart Veer [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=200203011808.g21I8XV11052@sheesh.cambridge.redhat.com \
    --to=bartv@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=guangbutun@hotmail.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).