source: trunk/README.developer @ 565

Last change on this file since 565 was 560, checked in by Peter Johansson, 16 years ago
  • Property svn:eol-style set to native
  • Property svn:keywords set to Id
  • Property svn:mime-type set to text/x-trac-wiki
File size: 5.6 KB
[84]1$Id: README.developer 560 2008-03-04 18:06:21Z peter $
[338]3= Developer Information =
5This file contains developer specific information.
8=== Coding style ===
10Developers should follow the coding style outlined in the
[560]11[ C++ coding guidelines].
14=== Subversion usage ===
16Commits should be minimalistic and the projects should always compile
[442]17(`make` and `make check`) when someone makes a clean checkout. There is
[394]18a short introduction to subversion and its usage available as
[560]19[ Subversion guidelines].
[394]20We follow these guidelines.
[481]23=== bootstrap and autoreconf ===
[481]25At first checkout from the repository you must run the bootstrapping
28  `./bootstrap`
[481]30to setup autoconf files. To push subsequent changes of this file into
31the build scripts you run
[481]33   `autoreconf`
[338]36=== configure ===
[387]38Run the generated configure script with
[555]40  `./configure --enable-debug`
42The option flag `--enable-debug` turns on debug options (e.g. enables
46=== Testing ===
48Test programs should be created and added to the `make check`
49execution. Always check that the test runs before committing code to
50the repository, i.e., run `make check`.
52There is a test repository in source:trunk/test/repo that is a part of
53the svndigest repository. The logic behind this is that it is nice to
54have a common test repository that can be used off-line. Changes to
55the repository are usually made to create new test cases and it is
56important that these changes are committed to svndigest repository as
57well. All changes to the test repository are not automatically
58propagated to the svndigest repository and it is important that some
59files created in the test repository are manually added to the
60svndigest repository. Assuming that `make check` is run before a
61commit, a warning is generated if the test repository is inconsistent
62with the svndigest repository. There will be a diagnostic message and
63a resolution hint, however the developer must examine and resolve the
64problem manually.
66The problem is simply that the file source:trunk/test/repo/db/current
67is changed compared to the svndigest repository. The `current` file
68indicates a specific number of change sets within the test repository
69and the directories source:trunk/test/repo/db/revs and
70source:trunk/test/repo/db/revprops contains a matching number of
71change sets. However, the change sets added to the test repository are
72not automatically added to the svndigest repository, therefore the new
73files in the `revs` and `revprops` directories must be added manually
74to the svndigest repository.
76There is also a race condition when developers make changes to the
77test repository simultaneously: It is easy to create severe conflicts
78in the test repository. Imaging the case when two developers adds test
79commits to the test repository, and then tries to add these to the
80svndigest repository. Since there are different versions of the same
81test repository revisions, the second developer committing to the
82svndigest will get messages about files being in the way. This is just
83one situation with possible conflicts. This conflict is of course
84resolved by the second developer having to throw away his changes and
85redo them after a new checkout of the test repository.
87The take home message is that developers should communicate with each
88other when changing the test repository in order to avoid to large
89repository conflicts. AND read the output of `make check`.
[494]92=== Output file structure ===
94A directory reflecting the parsed directory is generated for each
95combination of StatsType, Author, and LineType, which is located in
[496]96`<TARGET>/<ROOT>/StatsType/Author/LineType/`. Author may be, on top of
97each author in the repository, a directory ''all'' that is a sum over
98all Authors. In same fashion LineType may be any of the three
99linetypes but may also ''total'', which a sum over all linetypes. In
100each `<TARGET>/<ROOT>/StatsType` there are directories
101`images/LineType` that contain a structure reflecting the parsed
102directory with images for every combination of File, LineType, and
103StatsType. Images for different Authors are identical and therefore
104shared between authors.
[338]107=== Create a distribution ===
[338]109Create a distribution package with `make dist`. Remember to test
110the package with `make distcheck`. If required packages are installed
111in non-standard locations you need to pass this information to
112`distcheck`. This is done by using the variable
[499]115   `DISTCHECK_CONFIGURE_FLAGS="[OPTION]..." make distcheck`
117Usually you need to set DISTCHECK_CONFIGURE_FLAGS to whatever options
[555]118you pass to configure.
[394]121== Releasing ==
[408]128Copyright (C) 2005, 2006 Jari Häkkinen
[394]129Copyright (C) 2007 Jari Häkkinen, Peter Johansson
[547]130Copyright (C) 2008 Peter Johansson
[519]132This file is part of svndigest,
[149]134svndigest is free software; you can redistribute it and/or modify it
[84]135under the terms of the GNU General Public License as published by the
136Free Software Foundation; either version 2 of the License, or (at your
137option) any later version.
[149]139svndigest is distributed in the hope that it will be useful, but
140WITHOUT ANY WARRANTY; without even the implied warranty of
142General Public License for more details.
144You should have received a copy of the GNU General Public License
145along with this program; if not, write to the Free Software
146Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307,
Note: See TracBrowser for help on using the repository browser.