I ITP Tremulous for Debian
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363581) and have some
I have one source package and three binary packages : tremulous,
tremulous-data and tremulous-server
Here are the licenses :
- The main code is GPL : no problem
- The datas are CC-share-alike : non-free. They intend to relicense them
to CC 2.5+ then CC 3 when it will be out though, which will make them
- There is a not-free-at-all media license exception, but the author
agreed to change the license to CC as the other medias. He wrote an
email to the Tremulous maintainer for this, so I think it's ok to say
it's CC right now. The new relicensing is not included in my source
archive, but as he gave his agreement, I think I can just remove this
exception from the license file in my archive.
- There are some tools needed to compile some of the sources. Here is
their license :
The authors of this software are Christopher W. Fraser and
David R. Hanson.
Copyright (c) 1991,1992,1993,1994,1995,1996,1997,1998 by AT&T,
Christopher W. Fraser, and David R. Hanson. All Rights Reserved.
Permission to use, copy, modify, and distribute this software for any
purpose, subject to the provisions described below, without fee is
hereby granted, provided that this entire notice is included in all
copies of any software that is or includes a copy or modification of
this software and in all copies of the supporting documentation for
THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T MAKE ANY
REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY
OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
lcc is not public-domain software, shareware, and it is not protected
by a `copyleft' agreement, like the code from the Free Software
lcc is available free for your personal research and instructional use
under the `fair use' provisions of the copyright law. You may, however,
redistribute lcc in whole or in part provided you acknowledge its
source and include this CPYRIGHT file. You may, for example, include
the distribution in a CDROM of free software, provided you charge only
for the media, or mirror the distribution files at your site.
You may not sell lcc or any product derived from it in which it is a
significant part of the value of the product. Using the lcc front end
to build a C syntax checker is an example of this kind of product.
You may use parts of lcc in products as long as you charge for only
those components that are entirely your own and you acknowledge the use
of lcc clearly in all product documentation and distribution media. You
must state clearly that your product uses or is based on parts of lcc
and that lcc is available free of charge. You must also request that
bug reports on your product be reported to you. Using the lcc front
end to build a C compiler for the Motorola 88000 chip and charging for
and distributing only the 88000 code generator is an example of this
kind of product.
Using parts of lcc in other products is more problematic. For example,
using parts of lcc in a C++ compiler could save substantial time and
effort and therefore contribute significantly to the profitability of
the product. This kind of use, or any use where others stand to make a
profit from what is primarily our work, requires a license agreement
with Addison-Wesley. Per-copy and unlimited use licenses are
available; for more information, contact
J. Carter Shanklin
Addison Wesley Longman, Inc.
2725 Sand Hill Rd.
Menlo Park, CA 94025
Chris Fraser / email@example.com
David Hanson / firstname.lastname@example.org
$Revision: 145 $ $Date: 2001-10-17 16:53:10 -0500 (Wed, 17 Oct 2001) $
The parts about not being able to sell it are non-free, I think.
I don't intend to package them, but i have to include them in the source
package. The Makefile, called by the rules file, builds them and then
uses them to build the game. As they don't appear in the binary package,
I don't know if it makes the whole non-free of not.
As I have a single source package, and the datas are it in, is it right
to put the other packages in contrib (if the tools consideration permits
it) or do I have to make a separate source package for the datas (and
for the tools maybe) ?