From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19279 invoked by alias); 2 Feb 2004 15:29:16 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 19105 invoked from network); 2 Feb 2004 15:29:08 -0000 Date: Mon, 02 Feb 2004 15:29:00 -0000 To: sebastien Couret Cc: ecos-devel@sources.redhat.com, ecos-maintainers@ecos.sourceware.org Subject: Re: DHCP server package Message-ID: <20040202152854.GD2882@lunn.ch> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i From: Andrew Lunn X-SW-Source: 2004-02/txt/msg00001.txt.bz2 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. eCos uses a modified GPL license. The modification stops the GPL spreading from the licensed file to other files. So this allows people to do commercial applications with eCos. You should make it clear to anybody you distribute your epk to that its GPL and not the modified GPL used by the rest of eCos. Andrew