From 3f52e01c9a9e8c792609dcf01342d903272c1f14 Mon Sep 17 00:00:00 2001 From: bangerth Date: Thu, 13 Jul 2006 12:18:51 +0000 Subject: [PATCH] More on svn conversion git-svn-id: https://svn.dealii.org/trunk@13368 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/doc/development/testsuite.html | 36 +++++++++++++------------- deal.II/doc/development/toc.html | 4 +-- deal.II/doc/news/anisotropic.html | 2 +- deal.II/doc/reports/Makefile | 2 +- 4 files changed, 22 insertions(+), 22 deletions(-) diff --git a/deal.II/doc/development/testsuite.html b/deal.II/doc/development/testsuite.html index d451da6658..4902f408c2 100644 --- a/deal.II/doc/development/testsuite.html +++ b/deal.II/doc/development/testsuite.html @@ -5,7 +5,7 @@ The deal.II Testsuite - + @@ -43,7 +43,7 @@ cd dealtest make clean - cvs update -d -P + svn update make build-test BUILDTESTFLAGS='-with-umfpack -with-lapack' mail build-tests@dealii.org < build-test-log @@ -73,7 +73,7 @@ cd dealtest make clean - cvs update -d -P + svn update make build-test BUILDTESTFLAGS='CC=mycc CXX=myCC' mail build-tests@dealii.org < build-test-log @@ -85,7 +85,7 @@

Most of our tests are built in dedicated directories, i.e. work on copies of deal.II that we don't usually use to work on every day. We do this, - because we want to see if the version in the CVS repository can be + because we want to see if the version in the subversion repository can be compiled, not the version that we have made changes in.

@@ -98,9 +98,9 @@ export PATH=/my/compiler/path:$PATH export CXX=myCC - cvs checkout deal.II + svn co http://wolfgang.math.tamu.edu/svn/public/deal.II/trunk/deal.II cd deal.II - cvs update -d -P + svn update make build-test BUILDTEST=yes BUILDTESTFLAGS='CC=mycc CXX=myCC' mail build-tests@dealii.org < build-test-log cd .. @@ -122,7 +122,7 @@ deal.II has a testsuite that, at the time this article is written, has some 490 small programs that we run every time we make a change to make sure that no existing functionality is broken. The - expected output is also stored in our CVS archive, and when you + expected output is also stored in our subversion archive, and when you run a test you are notified if a test fails. These days, every time we add a significant piece of functionality, we add at least one new test to the testsuite, and we also do so if we fix a bug, @@ -144,11 +144,11 @@

Running it

- To run the testsuite, you first need CVS access to our source + To run the testsuite, you first need subversion access to our source repository. If you have that, do the following steps:

        cd /path/to/deal.II
-       cvs checkout tests
+       subversion checkout tests
     
This should generate a tests/ directory parallel to the base/, lac/, etc directories. Then @@ -169,7 +169,7 @@ Once you have done this, you may simply type make. This runs all the tests there are, but stops at the first one that fails to either execute properly or for which - the output does not match the expected output found in the CVS + the output does not match the expected output found in the subversion archive. This is helpful if you want to figure out if any test is failing at all. Typical output looks like this:
@@ -278,7 +278,7 @@
     test's name.) If this produces errors or triggers assertions, then you will
     want to use a debugger on the executable to figure out what happens. On
     the other hand, if you are sure that this also worked, you will
-    want to compare the output with the stored output from CVS:
+    want to compare the output with the stored output from subversion:
     
       make hierarchical/OK
     
@@ -521,18 +521,18 @@ testname/cmp/generic

Tests are a way to make sure everything keeps working. If they aren't automated, they are no good. We are therefore very - interested in getting new tests. If you have CVS write access + interested in getting new tests. If you have subversion write access already, you have to add the new test and the expected output file, and to commit them together with the changed Makefile, like so:

-      cvs add bits/my_new_test.cc 
-      cvs add bits/my_new_test
-      cvs add bits/my_new_test/cmp
-      cvs add bits/my_new_test/cmp/generic
-      cvs commit -m "New test" bits/my_new_test* bits/Makefile
+      subversion add bits/my_new_test.cc 
+      subversion add bits/my_new_test
+      subversion add bits/my_new_test/cmp
+      subversion add bits/my_new_test/cmp/generic
+      subversion commit -m "New test" bits/my_new_test* bits/Makefile
     
- If you don't have CVS write access, talk to us on the mailing + If you don't have subversion write access, talk to us on the mailing list; writing testcases is a worthy and laudable task, and we would like to encourage it by giving people the opportunity to contribute! diff --git a/deal.II/doc/development/toc.html b/deal.II/doc/development/toc.html index a6382c20fd..1526b67c8e 100644 --- a/deal.II/doc/development/toc.html +++ b/deal.II/doc/development/toc.html @@ -5,7 +5,7 @@ The deal.II Development Page - + @@ -21,7 +21,7 @@ be of interest if you want to develop programs based on deal.II yourself, or if you want to contribute to the development of deal.II itself. In the - latter case, we encourage you to get anonymous CVS access as + latter case, we encourage you to get anonymous subversion access as described on our download page.

diff --git a/deal.II/doc/news/anisotropic.html b/deal.II/doc/news/anisotropic.html index 5d587f60e0..f95ae2e3ee 100644 --- a/deal.II/doc/news/anisotropic.html +++ b/deal.II/doc/news/anisotropic.html @@ -13,7 +13,7 @@

Changes between the main branch and the anisotropic branch

-This is the list of changes between the main cvs branch and the +This is the list of changes between the main subversion branch and the anisotropic branch of deal.II library. It is subdivided into changes made to the three sub-libraries base, lac, and /dev/null) ; then \ echo "Checking `pwd`" ; \ -- 2.39.5