[svnbook] r5552 committed - branches/1.8/zh/book/ch05-repository-admin.xml

wuzhouhui at users.sourceforge.net wuzhouhui at users.sourceforge.net
Mon Dec 25 06:11:54 CST 2017


Revision: 5552
          http://sourceforge.net/p/svnbook/source/5552
Author:   wuzhouhui
Date:     2017-12-25 12:11:54 +0000 (Mon, 25 Dec 2017)
Log Message:
-----------
1.8/zh: translation of chapter 5 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch05-repository-admin.xml

Modified: branches/1.8/zh/book/ch05-repository-admin.xml
===================================================================
--- branches/1.8/zh/book/ch05-repository-admin.xml	2017-12-24 07:53:38 UTC (rev 5551)
+++ branches/1.8/zh/book/ch05-repository-admin.xml	2017-12-25 12:11:54 UTC (rev 5552)
@@ -494,6 +494,17 @@
           <primary>project root</primary>
         </indexterm>
 
+        项目的组织方式确定后, 接下来就要考虑仓库内部的目录结构. 因为 Subversion
+        在创建分支和标签时使用的是常规的目录拷贝操作 (见 <xref
+          linkend="svn.branchmerge"/>), Subversion 社区建议管理员为每一个项目
+        的根目录—包含了所有与项目相关的数据的 <quote>顶层</quote> 目录
+        —选择一个仓库位置, 然后在项目根目录下创建 3 个子目录:
+        <filename>trunk</filename> 是开发主线; <filename>branches</filename>
+        存放所有的分支; <filename>tags</filename> 存放所有的标签.<footnote>
+          <para><filename>trunk</filename>, <filename>tags</filename>
+            和 <filename>branches</filename> 这 3 者有时被称为 <quote>TTB
+              目录</quote></para></footnote></para>
+      <!--
         After deciding how to organize your projects with respect
         to repositories, you'll probably want to think about directory
         hierarchies within the repositories themselves.  Because
@@ -514,8 +525,12 @@
         <filename>tags</filename>, and <filename>branches</filename>
         trio is sometimes referred to as <quote>the TTB
         directories.</quote></para></footnote></para>
+      -->
 
+      <!--
       <para>For example, your repository might look like this:</para>
+      -->
+      <para>比如说, 仓库的目录结构可能是下面这样:</para>
 
       <informalexample>
         <literallayout>
@@ -536,6 +551,7 @@
 </literallayout>
       </informalexample>
 
+      <!--
       <para>Note that it doesn't matter where in your repository each
         project root is.  If you have only one project per repository,
         the logical place to put each project root is at the root of
@@ -545,6 +561,12 @@
         shared code in the same subdirectory, or maybe just grouping
         them alphabetically.  Such an arrangement might look
         like this:</para>
+      -->
+      <para>注意, 项目根目录在仓库中的位置并不重要. 如果每个仓库只包含一个项
+        目, 那么最常见的安排就是把仓库的根目录作为项目的根目录. 如果一个仓库
+        内包含了多个项目, 管理员可能会对它们进行分组, 例如把目标类似或共享代
+        码的项目放在同一个子目录内, 或者只是根据字母顺序进行分组. 一个例子是:
+      </para>
 
       <informalexample>
         <literallayout>
@@ -568,6 +590,7 @@
 </literallayout>
       </informalexample>
 
+      <!--
       <para>Lay out your repository in whatever way you see fit.
         Subversion does not expect or enforce a particular layout—in
         its eyes, a directory is a directory is a directory.
@@ -574,6 +597,10 @@
         Ultimately, you should choose the repository arrangement that
         meets the needs of the people who work on the projects that
         live there.</para>
+      -->
+      <para>管理员完全可以按照自己的喜好决定仓库的布局, Subversion 对仓库的布局
+        并没有特殊的要求—在它看来, 一个目录只是个目录而已. 总而言之,
+        仓库的布局应该满足项目及其开发人员的需求.</para>
 
       <para>In the name of full disclosure, though, we'll mention
         another very common layout.  In this layout, the




More information about the svnbook-dev mailing list