From 6207769d64eea01cb7ddeb083e62bc4a31932389 Mon Sep 17 00:00:00 2001 From: Richard Brooksby Date: Fri, 24 May 2002 14:00:08 +0100 Subject: [PATCH] Adding license.txt and readme.txt files to mps sources. Copied from Perforce Change: 29471 ServerID: perforce.ravenbrook.com --- mps/license.txt | 1 + mps/readme.txt | 1 + 2 files changed, 2 insertions(+) create mode 100644 mps/license.txt create mode 100644 mps/readme.txt diff --git a/mps/license.txt b/mps/license.txt new file mode 100644 index 00000000000..98c6a522c4f --- /dev/null +++ b/mps/license.txt @@ -0,0 +1 @@ + MEMORY POOL SYSTEM OPEN SOURCE LICENSE Copyright (C) 2001-2002 Ravenbrook Limited . All rights reserved. This is an open source license. Contact Ravenbrook for commercial licensing options. 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. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Redistributions in any form must be accompanied by information on how to obtain complete source code for the this software and any accompanying software that uses this software. The source code must either be included in the distribution or be available for no more than the cost of distribution plus a nominal fee, and must be freely redistributable under reasonable conditions. For an executable file, complete source code means the source code for all modules it contains. It does not include source code for modules or files that typically accompany the major components of the operating system on which the executable file runs. 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, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS AND 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. --- $Id$ \ No newline at end of file diff --git a/mps/readme.txt b/mps/readme.txt new file mode 100644 index 00000000000..33a28de880c --- /dev/null +++ b/mps/readme.txt @@ -0,0 +1 @@ +MEMORY POOL SYSTEM KIT README Richard Brooksby, Ravenbrook Limited, 2002-05-20 CONTENTS 1. Introduction 2. Getting started 3. The structure of the kit 4. Developing using the kit 5. Testing 6. Building and testing a release 7. Contributing your work 8. Getting help 9. Licensing A. References B. Document history C. Copyright and license 1. INTRODUCTION This is the Memory Pool System Kit -- a compelete set of sources for using, modifying, and adapting the MPS. The Memory Pool System (MPS) is a very general, adaptable, flexible, reliable, and efficient memory management system. It permits the flexible combination of memory management techniques, supporting manual and automatic memory management, in-line allocation, finalization, weakness, and multiple concurrent co-operating incremental generational garbage collections. It also includes a library of memory pool classes implementing specialized memory management policies. [Where to go for more details -- reference to overview document.] This document is a brief introduction to the kit. [Where to go for more details.] The readership of this document is anyone who wants to modify, adapt, or extend the MPS. This document is not confidential. 2. GETTING STARTED The MPS Kit is a complete set of sources and documentation to enable third parties to use, modify, and adapt the MPS. For Windows, the kit is distributed as the ZIP archive "mps-kit-1.100.0.zip". Unpack it using WinZip. For Unix and Mac OS X, the integration kit is distributed as the tarball "mps-kit-1.100.0.tar.gz". Unpack it using the command "gunzip -c mps-kit-1.100.0.tar.gz | tar xvf -", or by dropping the file onto StuffIt Expander under Mac OS X. The top-level file "index.html" in the sources indexes many other files, and is a good place to start. You should read the user manuals and the high level design documents. 3. THE STRUCTURE OF THE KIT The Integration Kit is a copy of the sources used to develop and maintain the MPS at Ravenbrook Limited . The "sources" are all the things that go to make up the product, not just source code files. For example, the sources for the manuals are here too, because we maintain them in parallel with the code. The sources at Ravenbrook are mirrored from our Perforce configuration management server onto our internal web server at info.ravenbrook.com, and are designed to be browsed on that server. You will find HTML documents which index many of the directories. Read these, starting with the top level "index.html". You might find some links to "info.ravenbrook.com" or "/project/mps/...". Sorry about that -- it's partly due to the nature of HTML links. You will find most project documents from the MPS Project page , including many documents which aren't "sources" but may still be useful to understand the history of the project. [A note about confidential sources being excluded.] 4. DEVELOPING USING THE KIT [See "Licensing"] 5. TESTING 6. BUILDING AND TESTING A RELEASE 7. CONTRIBUTING YOUR WORK We'd like to include improvements to the MPS in the distributions from Ravenbrook Limited. Please consider putting your work under an open source license and sending it to us. It will help a great deal if your work is self-consistent. This means that the documentation is up to date (even if only with sketchy but accurate notes) and the procedures have been maintained. 8. GETTING HELP You can obtain expert professional support for the MPS from Ravenbrook Limited , the developers of the MPS, who have many years of experience in commercial memory management systems. Write to us for more information. You might also want to join the MPS discussion mailing list. To join, send a message with the word "subscribe" in the body to mps-discussion-request@ravenbrook.com or send the word "help" for general information. 9. LICENSING The MPS is distributed under an open source license (see the file "license.txt"). The license is designed to make it possible for you to use the MPS in your own projects, provided that you either don't distribute your product, or your product is open source too. If you are developing a closed source product and want to use the MPS you must license under commercial terms from Ravenbrook Limited . Please write to us for more information. A. REFERENCES B. DOCUMENT HISTORY 2002-05-20 RB Created based on template from P4DTI project. C. COPYRIGHT AND LICENSE Copyright (C) 2001-2002 Ravenbrook Limited . All rights reserved. This is an open source license. Contact Ravenbrook for commercial licensing options. 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. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Redistributions in any form must be accompanied by information on how to obtain complete source code for the this software and any accompanying software that uses this software. The source code must either be included in the distribution or be available for no more than the cost of distribution plus a nominal fee, and must be freely redistributable under reasonable conditions. For an executable file, complete source code means the source code for all modules it contains. It does not include source code for modules or files that typically accompany the major components of the operating system on which the executable file runs. 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, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS AND 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. $Id$ \ No newline at end of file