From: Jonathan Larmour <jifl@eCosCentric.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: sebastien Couret <sebastien.couret@elios-informatique.fr>,
ecos-devel@sources.redhat.com,
ecos-maintainers@ecos.sourceware.org
Subject: Re: DHCP server package
Date: Mon, 02 Feb 2004 17:10:00 -0000 [thread overview]
Message-ID: <401E848A.5030502@eCosCentric.com> (raw)
In-Reply-To: <20040202152854.GD2882@lunn.ch>
Andrew Lunn wrote:
> On Mon, Feb 02, 2004 at 04:24:36PM +0100, sebastien Couret wrote:
>
>>Hi All,
>>
>>I have ported the uDHCP DHCP server to eCOS.
>>
>>I think this can be usefull , because for the momemt there is no DHCP server
>>package available with eCOS.
>>
>>As told in the FAQ, my contribution got the form of an epk package under GPL.
>>
>>I would like to have feedback, comments , bug reports and so on , from all
>>of you that could find it usefull.
>>
>>On the other hand, Can someone of you explain me how can this package
>>integrate the eCOS CVS ? and what is the process to follow ?
>
>
> GPL code cannot be integrated in the eCos CVS. The GPL license for
> uDHCP would mean that all of eCos had to be distributed as GPL. This
> would also mean that all of the application would also have to be
> GPL. We don't want this, since people use eCos for writing commercial
> applications.
What we can do though is make it available on the contribution download
page, <http://ecos.sourceware.org/contrib.html>. If this is okay by you
then mail me or Andrew the EPK off list and we'll put something up on that
page with your name in lights!
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
prev parent reply other threads:[~2004-02-02 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 15:21 sebastien Couret
2004-02-02 15:29 ` Andrew Lunn
2004-02-02 17:10 ` 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=401E848A.5030502@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=andrew@lunn.ch \
--cc=ecos-devel@sources.redhat.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=sebastien.couret@elios-informatique.fr \
/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).