|
1 | 1 |
|
2 | 2 | Developer's Frequently Asked Questions (FAQ) for PostgreSQL
|
3 | 3 |
|
4 |
| - Last updated: Fri Mar 11 06:42:00 EST 2005 |
| 4 | + Last updated: Fri Mar 11 06:43:43 EST 2005 |
5 | 5 |
|
6 | 6 | Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
7 | 7 |
|
|
139 | 139 | Basic system testing
|
140 | 140 |
|
141 | 141 | The easiest way to test your code is to ensure that it builds against
|
142 |
| - the latest verion of the code and that it does not generate compiler |
| 142 | + the latest version of the code and that it does not generate compiler |
143 | 143 | warnings.
|
144 | 144 |
|
145 | 145 | It is worth advised that you pass --enable-cassert to configure. This
|
|
155 | 155 | test suite. To do this, issue "make check" in the root directory of
|
156 | 156 | the source tree. If any tests failure, investigate.
|
157 | 157 |
|
158 |
| - If you've deliberately changed existing behaviour, this change may |
| 158 | + If you've deliberately changed existing behavior, this change may |
159 | 159 | cause a regression test failure but not any actual regression. If so,
|
160 | 160 | you should also patch the regression test suite.
|
161 | 161 |
|
|
382 | 382 | 1. A set of patches to make certain portions of the source tree
|
383 | 383 | 'behave' in the different environment of the RPMset;
|
384 | 384 | 2. The initscript;
|
385 |
| - 3. Any other ancilliary scripts and files; |
| 385 | + 3. Any other ancillary scripts and files; |
386 | 386 | 4. A README.rpm-dist document that tries to adequately document both
|
387 | 387 | the differences between the RPM build and the WHY of the
|
388 | 388 | differences, as well as useful RPM environment operations (like,
|
|
500 | 500 | want to contain the toplevel "pgsql" directory and say
|
501 | 501 | cvs ... checkout pgsql
|
502 | 502 |
|
503 |
| - To get a past branch, you cd to whereever you want it and say |
| 503 | + To get a past branch, you cd to wherever you want it and say |
504 | 504 | cvs ... checkout -r BRANCHNAME pgsql
|
505 | 505 |
|
506 | 506 | For example, just a couple days ago I did
|
|
560 | 560 | source code is available at
|
561 | 561 | http://gborg.postgresql.org/project/pgweb/projdisplay.php , the code
|
562 | 562 | for the next version of the website is under the "portal" module. You
|
563 |
| - will al so find code for the "techdocs" website if you would like to |
| 563 | + will also find code for the "techdocs" website if you would like to |
564 | 564 | contribute to that. A temporary todo list for current website
|
565 | 565 | development issues is available at http://xzilla.postgresql.org/todo
|
566 | 566 |
|
|
0 commit comments