ANNOUNCE: L4Env version 0.1
farid.hajji at ob.kamp.net
Tue Jul 1 12:40:24 CEST 2003
> > > Since L4env is _not_ entirely written from scratch. We depend on
> > > some imported stuff which is GPL.
> > Ah, okay. L4Env shouldn't therefore be used for NetBSD/L4 or
> > similar porting projects due to license clashes.
> are the L4_env IDL files dependent on GPLed sources. If not, you should
> change the license of the IDL files to something not so infective.
> If the IDL files are GPL, also the generated code, i.e. the client headers
> become GPL which in turn attempts to use your servers.
yes, that's exactly my concern. IDL files and header files
that get included in a port would immediately infect everything
else. I'm not sure wether I should even have a look at L4Env right
now, should a clean room implementation be needed.
> It might be fine
> for NETBSD / L4 if the servers provided within L4 Env are GPLed but if the
> interfaces to them are not.
As for NetBSD/L4: don't expect GPLed code to make it in the tree.
It wouldn't (and shouldn't) happen.
Is there a GPL-free documentation of the L4Env interfaces available?
This would at least help a little bit...
Farid Hajji -- Unix Systems and Network Management.
Quoth the Raven, "Nevermore." --Edgar Allan Poe.
More information about the l4-hackers