Index: openacs-4/packages/acs-core-docs/www/cvs-guidelines.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-guidelines.html,v diff -u -r1.10.2.12 -r1.10.2.13 --- openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 5 Aug 2016 14:27:22 -0000 1.10.2.12 +++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 19 Nov 2016 09:21:53 -0000 1.10.2.13 @@ -6,7 +6,7 @@

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

Using CVS with OpenACS

Getting Started

+

Using CVS with OpenACS

Getting Started

All OpenACS code is available anonymously. To get code anonymously, use the parameter -d:pserver:anonymous@cvs.openacs.org:/cvsroot immediately after cvs in a cvs command to check out or export code. @@ -43,38 +43,17 @@ To do so, create the file ~/.cvsrc with the contents: 

cvs -z6
-cvs -q
-

-z6 speeds up cvs access over the network quite a bit by enabling compressed -connection by default. -q suppresses some verbose output from commands. For example, it makes the output of cvs up much easier to read.

-

-
-

Administrator Note: These are the steps to grant CVS commit rights to a user:

-
    -

  1. Create the user's account. On cvs.openacs.org:

    sudo bash
+cvs -q

    -z6 speeds up cvs access over the network quite a bit by enabling compressed + connection by default. -q suppresses some verbose output from commands. For example, it makes the output of cvs up much easier to read.

    Administrator Note: These are the steps to grant CVS commit rights to a user:

    1. Create the user's account. On cvs.openacs.org:

      sudo bash
 /usr/sbin/useradd -c "Real Name" -G cvs -p passwd username
 /usr/sbin/usermod -G cvs,username username
-
      2. -

    2. Grant cvs access to the user account. On any machine, in a temporary directory:

      - 
      cvs -d :ext:cvs.openacs.org:/cvsroot co CVSROOT
+

    3. Grant cvs access to the user account. On any machine, + in a temporary directory: + 

      cvs -d :ext:cvs.openacs.org:/cvsroot co CVSROOT
 cd CVSROOT
-emacs avail

      Add an avail line of the form:

      - 
      avail|username|openacs-4
      - 
      cvs commit -m "added commit on X for username" avail
      -
      4. -
    -
    -
    -
    -
    -
    -
    -

    -
    -
    -
    -

    Branimir suggests an additional level of abstraction. If you put

    Host cvs-server
+emacs avail

    Add an avail line of the form:

    avail|username|openacs-4
    cvs commit -m "added commit on X for username" avail

Branimir suggests an additional level of abstraction. If you put

Host cvs-server
       HostName cvs.openacs.org
-      User yournamehere

into your ~/.ssh/config file, then you can use -d :ext:cvs-server:/cvsroot instead of -d :ext:cvs.openacs.org:/cvsroot. You can then change the definition of cvs-server by changing one file instead of editing hundreds of CVSROOT/Repository files.

Checkout for Package Development

If you are actively developing a non-core package, you + User yournamehere

into your ~/.ssh/config file, then you can use -d :ext:cvs-server:/cvsroot instead of -d :ext:cvs.openacs.org:/cvsroot. You can then change the definition of cvs-server by changing one file instead of editing hundreds of CVSROOT/Repository files.

Checkout for Package Development

If you are actively developing a non-core package, you should work from the latest core release branch. Currently this is oacs-5-9. This ensures that you are working on top of a stable OpenACS core, but still allows you to commit feature @@ -89,13 +68,13 @@ Inventory and Package maintainers and status for a list of available packages and their current state. -

Checkout for Core Development

If you are actively developing packages in the OpenACS +

Checkout for Core Development

If you are actively developing packages in the OpenACS Core, work from the HEAD branch. HEAD is used for active development of the next version of core OpenACS. It may be very buggy; it may not even install correctly. Do not use this branch for development of non-core features unless your work depends on some of the HEAD core work. To check out HEAD, omit the - -r tag.

To check out HEAD for development, which requires an OpenACS developer account:

cvs -d:ext:cvs.openacs.org:/cvsroot checkout acs-core

To check out HEAD anonymously:

cvs -d:pserver:anonymous@cvs.openacs.org:/cvsroot checkout acs-core

Checkout .LRN

+ -r tag.

To check out HEAD for development, which requires an OpenACS developer account:

cvs -d:ext:cvs.openacs.org:/cvsroot checkout acs-core

To check out HEAD anonymously:

cvs -d:pserver:anonymous@cvs.openacs.org:/cvsroot checkout acs-core

Checkout .LRN

.LRN consists of a given version openacs core, plus a set of packages. These are collectively packages together to form a distrubution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0. @@ -110,7 +89,7 @@ mv dotlrn/install.xml ..

Working with CVS

Once you have a checkout you can use some commands to track what has changed since you checked out your copy. cvs -n update does not change any files, but reports which changes have been updated or locally modified, or are not present in CVS. -

To update your files, use cvs update. This will merge changes from the repository with your local files. It has no effect on the cvs.openacs.org repository.

OpenACS CVS Concepts

Modules

+

To update your files, use cvs update. This will merge changes from the repository with your local files. It has no effect on the cvs.openacs.org repository.

OpenACS CVS Concepts

Modules

All OpenACS code resides within a single CVS module, openacs-4. (The openacs-4 directory contains code for all versions of OpenACS 4 and later, and .LRN 1 and later.) Checking out this module retrieves all openacs code of any type. For convenience, subsets of openacs-4 are repackaged as smaller modules.

acs-core contains only critical common packages. It does not have any user applications, such as forums, @@ -138,7 +117,7 @@ project-manager-all contains the packages required, in combination with acs-core, to run the project-manager package.

Each OpenACS package (i.e., directory in openacs-4/packages/) is also aliased as a module of the same name. -

+

Tags and Branches

Tags and Branches look similar in commands, but behave differently. A tag is a fixed point on a branch. Check out @@ -338,7 +317,7 @@ flag which defaults to no-effect wouldn't require a TIP. Added a new mandatory flag to an existing function would require a TIP. -

+

Informal Guidelines

Informal guidelines which may be obsolete in places and should be reviewed: @@ -444,4 +423,4 @@ backup with cvs

  • merging 2 file heirarchies with cvs -

    • Prev Home Next
    OpenACS Style Guide Up Release Version Numbering
    docs@openacs.org
    View comments on this page at openacs.org
    +

    Prev Home Next
    OpenACS Style Guide Up Release Version Numbering
    docs@openacs.org