1<?xml version="1.0" encoding="UTF-8" standalone="no"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 6 <title>Chapter��1.��Introduction to Porting Berkeley DB </title> 7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> 8 <meta name="generator" content="DocBook XSL Stylesheets V1.62.4" /> 9 <link rel="home" href="index.html" title="Porting Berkeley DB" /> 10 <link rel="up" href="index.html" title="Porting Berkeley DB" /> 11 <link rel="previous" href="preface.html" title="Preface" /> 12 <link rel="next" href="portprocess.html" title="Berkeley DB Porting Process" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Chapter��1.��Introduction to Porting Berkeley DB </th> 19 </tr> 20 <tr> 21 <td width="20%" align="left"><a accesskey="p" href="preface.html">Prev</a>��</td> 22 <th width="60%" align="center">��</th> 23 <td width="20%" align="right">��<a accesskey="n" href="portprocess.html">Next</a></td> 24 </tr> 25 </table> 26 <hr /> 27 </div> 28 <div class="chapter" lang="en" xml:lang="en"> 29 <div class="titlepage"> 30 <div> 31 <div> 32 <h2 class="title"><a id="introduction"></a>Chapter��1.��Introduction to Porting Berkeley DB </h2> 33 </div> 34 </div> 35 <div></div> 36 </div> 37 <div class="toc"> 38 <p> 39 <b>Table of Contents</b> 40 </p> 41 <dl> 42 <dt> 43 <span class="sect1"> 44 <a href="introduction.html#porttypes">Types of Berkeley DB ports</a> 45 </span> 46 </dt> 47 <dd> 48 <dl> 49 <dt> 50 <span class="sect2"> 51 <a href="introduction.html#id793975">When Oracle Has Agreed to Support Berkeley DB on the New Platform</a> 52 </span> 53 </dt> 54 <dt> 55 <span class="sect2"> 56 <a href="introduction.html#id794049">When Oracle has Not Agreed to Support Berkeley DB on the New Platform</a> 57 </span> 58 </dt> 59 </dl> 60 </dd> 61 <dt> 62 <span class="sect1"> 63 <a href="portprocess.html">Berkeley DB Porting Process</a> 64 </span> 65 </dt> 66 </dl> 67 </div> 68 <p> 69 Berkeley DB is an open source database product that supports a 70 variety of platforms. When there is a need to run Berkeley DB on a 71 platform that is currently not supported, DB is distributed in 72 source code form that you can use as base source to port Berkeley 73 DB to that platform. 74</p> 75 <p> 76 Before you begin actually porting Berkeley DB, you need an 77 understanding of the: 78</p> 79 <div class="itemizedlist"> 80 <ul type="disc"> 81 <li> 82 <p> 83 <a href="introduction.html#porttypes">Types of Berkeley DB ports</a> 84 </p> 85 </li> 86 <li> 87 <p> 88 <a href="portprocess.html">Berkeley DB Porting Process</a> 89 </p> 90 </li> 91 </ul> 92 </div> 93 <div class="sect1" lang="en" xml:lang="en"> 94 <div class="titlepage"> 95 <div> 96 <div> 97 <h2 class="title" style="clear: both"><a id="porttypes"></a>Types of Berkeley DB ports</h2> 98 </div> 99 </div> 100 <div></div> 101 </div> 102 <p> 103 There are several types of Berkeley DB ports: 104 </p> 105 <div class="itemizedlist"> 106 <ul type="disc"> 107 <li> 108 <p> 109 Ports developed and supported by Oracle 110 </p> 111 </li> 112 <li> 113 <p> 114 Ports developed by a customer or a partner, but which Oracle has 115 agreed to support. 116 </p> 117 </li> 118 <li> 119 <p> 120 Ports developed, maintained, and supported by a customer or partner. 121 </p> 122 </li> 123 </ul> 124 </div> 125 <p> 126 For a port developed by a customer or a partner, the general steps for porting 127 Berkeley DB to a new platform are the same whether or not Oracle has agreed to 128 support Berkeley DB on the new platform. For example, after you complete the port 129 you send it to Berkeley DB as described in <a href="sourceintegrate.html">Integrating Changes into the Berkeley DB Source Code</a>. 130 However, there are some differences. 131 </p> 132 <div class="sect2" lang="en" xml:lang="en"> 133 <div class="titlepage"> 134 <div> 135 <div> 136 <h3 class="title"><a id="id793975"></a>When Oracle Has Agreed to Support Berkeley DB on the New Platform</h3> 137 </div> 138 </div> 139 <div></div> 140 </div> 141 <p> 142 When porting Berkeley DB to a platform that Oracle has agreed to support, 143 you need to have Berkeley DB engineering review your port at various points. 144 These review points are discussed more fully in 145 <a href="sourceintegrate.html">Integrating Changes into the Berkeley DB Source Code</a>, 146 <a href="modifytest.html">Modifying the Tests</a>, and 147 <a href="testreview.html">Reviewing the Results of the Tests</a>. 148 </p> 149 <p> 150 It is up to you to submit the results of the tests (test_micro, 151 test_os, test_mutex, and, if possible, the entire tcl test 152 suit) for review by Oracle Berkelely DB engineering in order for Oracle to 153 consider providing support for Berkeley DB on a new platform. 154 </p> 155 <p> 156 You must also assign copyrights for your changes to any part of Berkeley DB 157 to "Oracle Corporation" and attest to the fact that you are not infringing 158 on any software patents for the changes to be included in the general 159 Berekely DB distribution. 160 </p> 161 <p> 162 Once the port is certified, Oracle provides support for Berkeley DB on the 163 new platform in the same manner that it does for Berkeley DB running on 164 other established platforms. 165 </p> 166 </div> 167 <div class="sect2" lang="en" xml:lang="en"> 168 <div class="titlepage"> 169 <div> 170 <div> 171 <h3 class="title"><a id="id794049"></a>When Oracle has Not Agreed to Support Berkeley DB on the New Platform</h3> 172 </div> 173 </div> 174 <div></div> 175 </div> 176 <p> 177 When Oracle has <span class="emphasis"><em>not</em></span> agreed to support 178 Berkeley DB on the new platform, the customer or partner assume the 179 responsibility of front-line support. When it is determined that there is a 180 problem in the code that was not modified by the customer or partner, then 181 Berkeley DB engineering provides support to the customer or vendor who 182 implemented the port, However, in these cases, Oracle needs access to the 183 platform and hardware for diagnosing, debugging, and testing. 184 185 </p> 186 </div> 187 </div> 188 </div> 189 <div class="navfooter"> 190 <hr /> 191 <table width="100%" summary="Navigation footer"> 192 <tr> 193 <td width="40%" align="left"><a accesskey="p" href="preface.html">Prev</a>��</td> 194 <td width="20%" align="center"> 195 <a accesskey="u" href="index.html">Up</a> 196 </td> 197 <td width="40%" align="right">��<a accesskey="n" href="portprocess.html">Next</a></td> 198 </tr> 199 <tr> 200 <td width="40%" align="left" valign="top">Preface��</td> 201 <td width="20%" align="center"> 202 <a accesskey="h" href="index.html">Home</a> 203 </td> 204 <td width="40%" align="right" valign="top">��Berkeley DB Porting Process</td> 205 </tr> 206 </table> 207 </div> 208 </body> 209</html> 210