[Gnu-arch-users] Another way of saying the same thing

[Pierce T . Wetter III]

As before, comments appreciated, since this is my regurgitation of my 
understanding of the tutorial...


 Organizing your source.

 There are 4 ways of organizing your source code in arch:

   1. By archive.

     Since you can have multiple archives, you can organize your source 
that way.
     This is most useful for collections of related source that you 
want to keep
     together. In general, you want code that you revise together to be 
in a
     single archive. If you find yourself saying "you need this version 
from
     this archive, and this version from this archive", then it would 
probably
     be best to combine them into a single archive.

     For instance, if you have a database library, it might make sense
     to have that live in its own archive if its independent source .
     If however, you have a product that
     uses that library, and you are constantly adding features to the 
library in
     order to support the product, then they probably belong on the 
same archive
     under different categories.

   2. By category

     You can have multiple categories in each archive, so that's 
another method
     of organization. Categories tend to map to individual projects in
     collection of source.

   3. By branch

     While archives and categories let you organize your source code, 
branches let
     you organize by task. Generally, your task will probably be to 
work on the
     main line of development, but perhaps you need to port a project 
to a new
     operating system. In that case, you'd use a branch to hold all the 
changes
     for the new os.

   4. By version

     Guessing:

     Many projects if not all projects have the concept of a "release".
     While functionally they are similar to branches, versions let you 
set mile
     markers in your source so that you can mark particular points in 
the
     development stream.

Pierce