This file is indexed.

/usr/share/doc/gnat-gps/html/Version-Control-System.html is in gnat-gps-doc 5.0-6.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
<html lang="en">
<head>
<title>Version Control System - Using the GNAT Programming Studio</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Using the GNAT Programming Studio">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="prev" href="Debugging.html#Debugging" title="Debugging">
<link rel="next" href="Tools.html#Tools" title="Tools">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 2002-2010 AdaCore.

This document is free; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.

This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, see `http://www.gnu.org/licenses/'.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
  pre.display { font-family:inherit }
  pre.format  { font-family:inherit }
  pre.smalldisplay { font-family:inherit; font-size:smaller }
  pre.smallformat  { font-family:inherit; font-size:smaller }
  pre.smallexample { font-size:smaller }
  pre.smalllisp    { font-size:smaller }
  span.sc    { font-variant:small-caps }
  span.roman { font-family:serif; font-weight:normal; } 
  span.sansserif { font-family:sans-serif; font-weight:normal; } 
pre.smallexample {background-color:rgb(240,240,240);
                     font-family: courier new,courier,fixed;
                     font-size: 14px;
                     margin: 0px 40px 0px 40px;
                     border-width: 1px 2px 2px 1px;
                     border-top-style: dotted;
                     border-left-style: dotted;
                     border-right-style: solid;
                     border-bottom-style: solid;
                     border-color: black;}
   code             {color:black;
                     font-family: courier new,courier,fixed;
                     font-size: 14px;}
   body             {font-family: arial,helvetica,sans-serif;
                     font-size: 16px;
                     max-width: 800px;
                     text-align: justify}
   samp             {font-family: courier new,courier,fixed;
                     font-size: 14px}
                    
--></style>
</head>
<body>
<div class="node">
<a name="Version-Control-System"></a>
<p>
Next:&nbsp;<a rel="next" accesskey="n" href="Tools.html#Tools">Tools</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="Debugging.html#Debugging">Debugging</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="index.html#Top">Top</a>
<hr>
</div>

<h2 class="chapter">12 Version Control System</h2>

<p><a name="index-version-control-580"></a><!--  -->

<ul class="menu">
<li><a accesskey="1" href="The-VCS-Explorer.html#The-VCS-Explorer">The VCS Explorer</a>
<li><a accesskey="2" href="The-VCS-Activities.html#The-VCS-Activities">The VCS Activities</a>
<li><a accesskey="3" href="The-VCS-Menu.html#The-VCS-Menu">The VCS Menu</a>
<li><a accesskey="4" href="The-Version-Control-Contextual-Menu.html#The-Version-Control-Contextual-Menu">The Version Control Contextual Menu</a>
<li><a accesskey="5" href="Working-with-global-ChangeLog-file.html#Working-with-global-ChangeLog-file">Working with global ChangeLog file</a>
<li><a accesskey="6" href="The-Revision-View.html#The-Revision-View">The Revision View</a>
</ul>

   <p>GPS offers the possibility for multiple developers to work on the same project,
through the integration of version control systems (VCS). Each project can be
associated to a VCS, through the <code>VCS</code> tab in the Project properties
editor. See <a href="The-Project-Properties-Editor.html#The-Project-Properties-Editor">The Project Properties Editor</a>.

   <p>GPS does not come with any version control system: it uses underlying
command-line systems such as Subversion or ClearCase to perform
the low level operations, and provides a high level user interface on
top of them. Be sure to have a properly installed version control
system before enabling it under GPS.

   <p>The systems that are supported out of the box in GPS are:

     <dl>
<dt><b>Auto</b><dd><a name="index-VCS_002c-auto-581"></a>GPS can be setup to auto-detect the actual VCS to use for each
project. This is done by selecting <code>Auto</code> in the <code>VCS</code> tab
of the Project properties editor. See <a href="The-Project-Properties-Editor.html#The-Project-Properties-Editor">The Project Properties Editor</a>. 
This is also the default behavior when no VCS is specified in the project.

     <br><dt><b>ClearCase</b><dd><a name="index-VCS_002c-ClearCase-582"></a>
The standard ClearCase interface, which is built-in and uses a generic GPS
terminology for VCS operations.

     <p>Note that, at the moment, only Snapshot Views are supported in the
ClearCase integration; Dynamic Views are not supported.

     <br><dt><b>ClearCase Native</b><dd><a name="index-VCS_002c-ClearCase-Native-583"></a>
Which is fully customizable and uses by default the terminology
specific to ClearCase.

     <p>Note that, at the moment, only Snapshot Views are supported in the
ClearCase integration; Dynamic Views are not supported.

     <br><dt><b>CVS</b><dd><a name="index-VCS_002c-CVS-584"></a>
The Concurrent Version System.

     <p>GPS needs a corresponding <samp><span class="command">patch</span></samp> command that usually comes with it.

     <br><dt><b>Git</b><dd><a name="index-VCS_002c-Git-585"></a>
Distributed fast source code management. Support for Git on GPS is
partial. Basic commands are supported but the full power of Git (like
working with the index) is only available on the command line.

     <p>GPS needs a corresponding <samp><span class="command">diff</span></samp> command that usually comes with it.

     <br><dt><b>Subversion</b><dd><a name="index-VCS_002c-Subversion-586"></a>
The Subversion version control system. Note that on Windows this
version is intended to be used with Cygwin/Subversion and fully supports the
Cygwin path names.

     <p>GPS needs a corresponding <samp><span class="command">patch</span></samp> and <samp><span class="command">diff</span></samp> command
that usually comes with it.

     <br><dt><b>Subversion Windows</b><dd><a name="index-VCS_002c-Subversion-Windows-587"></a>
The Windows native Subversion version control system. The external
Subversion commands are expected to be built for the Win32
subsystem. This version does not support Cygwin path names.

     <p>GPS needs a corresponding <samp><span class="command">patch</span></samp> and <samp><span class="command">diff</span></samp> command
that usually comes with it. 
</dl>

   <p>The default VCS that GPS will use is "Auto" by default, and this can be
 configured through <a href="The-Preferences-Dialog.html#The-Preferences-Dialog">The Preferences Dialog</a>.

   <p>It is also possible to add your own support for other version control systems,
or modify one of the existing interfaces, see
<a href="Adding-support-for-new-Version-Control-Systems.html#Adding-support-for-new-Version-Control-Systems">Adding support for new Version Control Systems</a> for more information.

   <p>It is recommended that you first get familiar with the version control
system that you intend to use in GPS first, since many concepts used in GPS
assume basic knowledge of the underlying system.

   <p>Associating a VCS to a project enables the use of basic VCS features on the
source files contained in the project. Those basic features typically include
the checking in and out of files, the querying of file status, file revision
history, comparison between various revisions, and so on.

   <p><a name="index-password-588"></a>Note: the set-up must make sure that the VCS commands can be launched without
entering a password.

   </body></html>