Changes between Version 5 and Version 6 of pm-svn-server


Ignore:
Timestamp:
Jan 18, 2010 7:40:29 AM (11 years ago)
Author:
tkr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • pm-svn-server

    v5 v6  
    4040There are several configuration files. Some live in the "`conf`" subdirectory of the root of the repository, some live in "`conf`" subdirectories that are siblings of "`trunk`" or "`releases`" subdirectories. These are;
    4141
    42 `nightlytrunk.txt`::
     42=== nightlytrunk.txt ===
     43
    4344  Lives in a "`conf`" subdirectory that is a sibling of a "`trunk`". The existence (or non-existence) of the file controls whether a nightly tarball is created from the corresponding "`trunk`" (see above). The content of the file is irrelevant.
    4445
    45 `nonightlyreleases.txt`::
     46=== nonightlyreleases.txt ===
     47
    4648  Lives in a "`conf`" subdirectory that is a sibling of a "`releases`". The existence (or non-existence) of the file controls whether tarballs are created from the subdirectories of the corresponding "`releases`" (see above). The content of the file is irrelevant.
    4749
    48 `nolatest.txt`::
     50=== nolatest.txt ===
     51
    4952  Lives in a "`conf`" subdirectory that is a sibling of a "`releases`". The existence (or non-existence) of the file controls whether the "latest" file is created for the subproject the "`releases`" directory corresponds to (see above). The content of the file is irrelevant.
    5053
    51 `norelease.txt`::
     54=== norelease.txt ===
     55
    5256  Lives in a "`releases/M.m.t`" subdirectory. The existence (or non-existence) of the file controls whether a tarball should be created from the "`M.m.t`" release or not. If this file exists then  no tarball is created from this release even if the "`nonightlyreleases.txt`" file does not exist. The content of the file is irrelevant.
    5357
    54 `release.txt`::
     58=== release.txt ===
     59
    5560  Lives in the "`conf`" subdirectory of the root of the repository. This file '''must''' be committed alone. The project manager can use this file to create individual tarball releases from any part of the repository. Note that if a tarball is created then if a "`doxydoc/doxygen.conf`" file exists within the release then a tarball with the doxygen documentation will also be created. The format of this file is the following:
    5661 * lines starting with a `#` are discarded.
     
    7075  * "`replacedox`" is set to "`yes`"
    7176
    72 `perms.txt`::
     77=== perms.txt ===
     78
    7379  Lives in the "`conf`" subdirectory of the root of the repository. The project manager can excercise access control using this file. This file '''must''' be committed alone. For project "`Foo`" the file must contain an arbitrary number of blocks of the following format:
    7480{{{
     
    7985  I.e., for a given path a number of users have read-write access (everybody has read access). Unfortunately, at this time regular expressions can't be used. The userids specfied are the ones the users created for themselves by registering in Trac on the coin-or website. Also '''only those userids can be specified whose owners have already submitted a Contributor's Statement of Respect for Ownership to the COIN-OR foundation'''. If another userid is included then the commit will be rejected.
    8086
    81 `projDesc.xml`::
     87=== projDesc.xml ===
     88
    8289  Lives in the "`conf`" subdirectory of the root of the repository. Edit the template [https://projects.coin-or.org/BuildTools/raw-attachment/wiki/pm-svn-server/projDesc.xml here] to contain the relevant information for your project and simply check it into the repository in the {{{conf/}}} subdirectory of your repository's root (important: do not change the filename from {{{projDesc.xml}}}). After checking in this file, the project's information page will be automatically rendered from the information in this XML file when a user types in the address http://www.coin-or.org/projects/projName.xml, where "projName" is the official acronym of your project, i.e., the one that appears after https://projects.coin-or.org/ in order to get to your projects' Trac page. For example, the XML page of Cbc is [https://projects.coin-or.org/Cbc/browser/conf/projDesc.xml here], and Cbc's project information page is [http://www.coin-or.org/projects/Cbc.xml here].
    8390