Re: [ECOS] ecos license question.

[Jonathan Larmour <jifl at eCosCentric dot com>]

Shannon Holland wrote:
> On Wednesday, January 15, 2003, at 06:19  AM, Jonathan Larmour wrote:
>
> > The only code you can keep to yourself are files containing no eCos 
> > code in part or full.
> As I'm moving towards developing a commercial application, I'm also 
> interested in making sure I fully understand this.
>
> So my own code (which might include ecos header files and call ecos) is 
> covered by whatever license I choose to give it. If I make changes to 
> ecos itself, I need to make them public (and have absolutely no problem 
> with doing so!). If I copy some section of ecos code and put it in my 
> own, I need to make that part public.
Yep, all correct.

> As far as making code public, is giving my ecos changes back to the ecos 
> source tree/development group adequate or do I need to make the source 
> files available separately as well?
That's probably adequate, as long as you tell the people who use your code 
that that's where it came from.

By the strict definition of the GPL though, they _could_ ask for the exact 
sources you used to build with.

Jifl
--
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


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