diff options
author | Robin H. Johnson <robbat2@gentoo.org> | 2015-08-08 13:49:04 -0700 |
---|---|---|
committer | Robin H. Johnson <robbat2@gentoo.org> | 2015-08-08 17:38:18 -0700 |
commit | 56bd759df1d0c750a065b8c845e93d5dfa6b549d (patch) | |
tree | 3f91093cdb475e565ae857f1c5a7fd339e2d781e /licenses/fmod-3.75 | |
download | gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.gz gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.bz2 gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.zip |
proj/gentoo: Initial commit
This commit represents a new era for Gentoo:
Storing the gentoo-x86 tree in Git, as converted from CVS.
This commit is the start of the NEW history.
Any historical data is intended to be grafted onto this point.
Creation process:
1. Take final CVS checkout snapshot
2. Remove ALL ChangeLog* files
3. Transform all Manifests to thin
4. Remove empty Manifests
5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$
5.1. Do not touch files with -kb/-ko keyword flags.
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests
X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project
X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration
X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn
X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts
X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration
X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging
X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
Diffstat (limited to 'licenses/fmod-3.75')
-rw-r--r-- | licenses/fmod-3.75 | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/licenses/fmod-3.75 b/licenses/fmod-3.75 new file mode 100644 index 000000000000..4ac4e9b01c20 --- /dev/null +++ b/licenses/fmod-3.75 @@ -0,0 +1,45 @@ +Note: This license is from README.txt included in fmodapi375linux.tar.gz + +---------------------------------------------------------------------------- + FMOD 3.75 + Copyright (c) Firelight Technologies Pty, Ltd, + 1994 - 2004 +---------------------------------------------------------------------------- + + http://www.fmod.org + +---------------------------------------------------------------------------- +FMOD End User License Agreement +---------------------------------------------------------------------------- + +FMOD's names, sources, documentation and binaries contained within the +distributed archive are copyright © Firelight Technologies, Pty, Ltd. +1994-2004. + +The contents of the FMOD distribution archive may not be redistributed, +reproduced, modified, transmitted, broadcast, published or adapted in any +way, shape or form, without the prior written consent of the owner, +Firelight Technologies, be it by tangible or non tangible media. +The dynamically linkable files from the FMOD distribution archive may be +redistributed without the authors prior permission, and must remain unmodified. +The use of dll 'static linking' tools that aim to hide the fmod library are +forbidden. + +FMOD may not be used in a commercial product, or product that directly or +indirectly receives income with the aid of the FMOD sound library, without +a commercial license from Firelight Technologies. Releasing a product +without a commercial license in this instance is a breach of the FMOD EULA +and parties who violate this license will be prosecuted under the full +extent of the law. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS +``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 REGENTS OR +CONTRIBUTORS 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. |