aboutsummaryrefslogtreecommitdiff
path: root/COPYRIGHT.TXT
diff options
context:
space:
mode:
authorrhatto <rhatto@370017ae-e619-0410-ac65-c121f96126d4>2007-04-13 00:34:57 +0000
committerrhatto <rhatto@370017ae-e619-0410-ac65-c121f96126d4>2007-04-13 00:34:57 +0000
commit3a073be7dbe711da523f5d7d0a364d187c89b8bd (patch)
tree0ce0e4297ec83dcb6e2622f16bb8306353e15ad6 /COPYRIGHT.TXT
parentaa56e2c135e46ebe9097e37b97f8f5cf874b0845 (diff)
downloadslackbuilds-3a073be7dbe711da523f5d7d0a364d187c89b8bd.tar.gz
slackbuilds-3a073be7dbe711da523f5d7d0a364d187c89b8bd.tar.bz2
added COPYRIGHT.TXT
git-svn-id: svn+slack://slack.fluxo.info/var/svn/slackbuilds@1169 370017ae-e619-0410-ac65-c121f96126d4
Diffstat (limited to 'COPYRIGHT.TXT')
-rw-r--r--COPYRIGHT.TXT72
1 files changed, 72 insertions, 0 deletions
diff --git a/COPYRIGHT.TXT b/COPYRIGHT.TXT
new file mode 100644
index 00000000..9690b77b
--- /dev/null
+++ b/COPYRIGHT.TXT
@@ -0,0 +1,72 @@
+If you have any doubts about licensing on slack.sarava.org distributed scripts
+or found anything missing, please write to slack at listas.sarava.org.
+
+Here comes all non-GPL related licenses, mostly from build scripts we grabbed
+from third parties.
+
+----------------
+
+The Slackware Installation scripts are:
+
+ Copyright 1993, 1994, 1995, 1996, 1997, 1998, 1999 Patrick Volkerding, Moorhead, Minnesota, USA.
+ Copyright 2001, 2002, 2003, 2004, 2005 Slackware Linux, Inc. Concord, CA, USA.
+ Copyright 2005, 2006 Patrick J. Volkerding, Sebeka, MN, USA.
+ All rights reserved.
+
+ Redistribution and use of this software, with or without modification, is
+ permitted provided that the following conditions are met:
+
+ 1. Redistributions of this software must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+
+ 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.
+
+----------------
+
+Slackware is a registered trademark of Patrick Volkerding and Slackware Linux, Inc.
+Permission to use the Slackware trademark to refer to the Slackware distribution
+of Linux is hereby granted if the following conditions are met:
+
+1. In order to be called "Slackware", the distribution may not be altered
+ from the way it appears on the central FTP site (ftp.slackware.com). This
+ is to protect the integrity, reliability, and reputation of the Slackware
+ distribution. (Note that moving entire directories like "source" or
+ "contrib" to a second CD-ROM is allowable, but leaving them out and
+ distributing a single source-free disc is *not*, as indicated below)
+ Anyone wishing to distribute an altered version must have the changes
+ approved by volkerdi@slackware.com (i.e. certified to be reasonably
+ bug-free). If the changed distribution meets the required standards for
+ quality, then written permission to use the Slackware trademark may be
+ provided.
+
+2. All related source code must be included. (This is also required by the
+ GNU General Public License)
+
+3. Except by written permission from Slackware Linux, Inc., the Slackware
+ trademark may not be used as (or as part of) a product name, company
+ name, or registered domain name.
+
+4. Any approved use of "Slackware" must be followed by a circle-R, and must
+ acknowledge our ownership of the mark.
+
+Note that you can still redistribute a distribution that doesn't meet these
+criteria, you just can't call it "Slackware". Personally, I hate restricting
+things in any way, but these restrictions are not designed to make life
+difficult for anyone. I just want to make sure that bugs are not added to
+commercial redistributions of Slackware. They have been in the past, and
+the resulting requests for help have flooded my mailbox! I'm just trying to
+make sure that I have some recourse when something like that happens.
+
+Any questions about this policy should be directed to:
+ Patrick Volkerding <volkerdi@slackware.com>
+
+