On Fri, 2006-06-30 at 07:49, Eric Spakman wrote:
> > http://software.newsforge.com/article.pl?sid=06/06/23/1728205&tid=150
> > This obligation is specified even more strongly in section 10 of
> > the draft for the third version of the GPL, which specifically states that
> > "downstream users" (those who, like Woodford, adopt
> > the work of another project -- the "upstream distributor" -- for their own
> > use) fall under these obligations.
> >
> I still don't read that Bering-uClibc is not compliant, in the case of
> MEPIS and DSL they use packages from other projects AFAIK. We create our
> own binaries/packages from sources and patches we also provide and don't
> adopt from other distributions.
Eric,
That is a distinction of note, and it may place bering-uclibc within
compliance.
Now all that's left is to verify Wisp-Dist is compliant.
> I can't believe the restrictions are as tough as this, and if they are I
> still think Bering-uClibc is compliant or can easely be made compliant.
I think to be safe, we should release source tarballs with binary
release in the SF FRS.
RE: packages
I think we should tarball release binary and source collections
periodically in the SF FRS.
--
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
