On 2004-10-19 16:38+0100, Joe Orton wrote:
> copied and munged without bothering with the whole copyright business.
The case is that Subversion itself is breaking Neon's LGLP, isn't it?
5. ... However, linking a "work that uses the Library" with the
Library creates an executable that is a derivative of the Library
(because it contains portions of the Library), rather than a "work
that uses the library". The executable is therefore covered by this
License. Section 6 states terms for distribution of such
6. ... If the work during execution displays copyright notices, you
must include the copyright notice for the Library among them, as
well as a reference directing the user to the copy of this
License. Also, you must do one of these things: ...
Similar thing happens with OpenSSL:
* 6. Redistributions of any form whatsoever must retain the following
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
But I don't know hows resposibility is it to produce that, should there be a
hook in the neon, which will print that out, if neon is compiled with
svn, version 1.2.0 (dev build)
compiled Oct 18 2004, 06:54:11
Copyright (C) 2000-2004 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (http://www.Collab.Net/).
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV)
- handles 'http' schema
- handles 'https' schema
* ra_local : Module for accessing a repository on local disk.
- handles 'file' schema
* ra_svn : Module for accessing a repository using the svn network
- handles 'svn' schema
I think this should be fixed, because we are using our own advertise
clause in the CollabNet license, and we are printing it with
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Oct 19 18:15:00 2004