Re: Is the LLVM Release License DFSG-compatible?
On Wed, 2005-01-05 at 06:20 +0000, Matthew Garrett wrote:
> Al Stone <ahs3@fc.hp.com> wrote:
>
> > The remainder of LLVM is covered by the LLVM Release License
> > (see http://llvm.cs.uiuc.edu/releases/1.4/LICENSE.TXT) which is
> > actually the University of Illinois/NCSA Open Source License.
> > The University of Illinois/NCSA (UI/NCSA) license is very similar
> > to the MIT or BSD license, and software distributed under the
> > UI/NCSA license is OSI Certified Open Source Software (please
> > see http://www.opensource.org/licenses/UoI-NCSA.php).
>
> It's generally easier if you include a copy of the license, but having
> looked at this one I can't see any problem - it's basically 3 clause
> BSD. The only issue I can think of is the mention of third party code -
> have you checked the licenses of the subtrees named at the bottom of the
> license?
Ah, of course, that was silly of me not to. My apologies for not
including the license to begin with. I also did not realize that
evolution was not including the right mail headers for replies.
You learn something new every day...
I did check the "licenses" of the subtrees. With one exception,
these were notes on who actually owned the copyright to the works,
and not new or different licenses. The exception was for the bzip2
library, which contained the following (again, BSD-like):
This program, "bzip2" and associated library "libbzip2", are
copyright (C) 1996-2002 Julian R Seward. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. The origin of this software must not be misrepresented; you must
not claim that you wrote the original software. If you use this
software in a product, an acknowledgment in the product
documentation would be appreciated but is not required.
3. Altered source versions must be plainly marked as such, and must
not be misrepresented as being the original software.
4. The name of the author may not be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Julian Seward, Cambridge, UK.
jseward@acm.org
bzip2/libbzip2 version 1.0.2 of 30 December 2001
Thanks for all the feedback.
--
Ciao,
al
----------------------------------------------------------------------
Al Stone Alter Ego:
Linux & Open Source Lab Debian Developer
Hewlett-Packard Company http://www.debian.org
E-mail: ahs3@fc.hp.com ahs3@debian.org
----------------------------------------------------------------------
Reply to: