This file is indexed.

/usr/share/doc/gnat-gps/html/Custom-VCS-interfaces.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
<html lang="en">
<head>
<title>Custom VCS interfaces - 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="up" href="Adding-support-for-new-Version-Control-Systems.html#Adding-support-for-new-Version-Control-Systems" title="Adding support for new Version Control Systems">
<link rel="next" href="Describing-a-VCS.html#Describing-a-VCS" title="Describing a VCS">
<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="Custom-VCS-interfaces"></a>
<p>
Next:&nbsp;<a rel="next" accesskey="n" href="Describing-a-VCS.html#Describing-a-VCS">Describing a VCS</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Adding-support-for-new-Version-Control-Systems.html#Adding-support-for-new-Version-Control-Systems">Adding support for new Version Control Systems</a>
<hr>
</div>

<h4 class="subsection">16.9.1 Custom VCS interfaces</h4>

<p class="noindent">The Version Control interface in GPS can be customized, either to
refine the behavior of the existing system and adapt it to specific
needs, or to add support for other Version Control systems.

   <p>Custom VCS interfaces are defined entirely through XML files. Those
files are read in the same location as all the other XML
customizations that GPS offers. See <a href="Customizing-through-XML-and-Python-files.html#Customizing-through-XML-and-Python-files">Customizing through XML and Python files</a> for a
complete description.

   <p>There are two steps to follow when creating a custom VCS
interface. The first step is to describe the VCS itself, and the
second step is to implement actions corresponding to all the
operations that this VCS can perform. The following two sections
(<a href="Describing-a-VCS.html#Describing-a-VCS">Describing a VCS</a> and <a href="Implementing-VCS-actions.html#Implementing-VCS-actions">Implementing VCS actions</a>) describe
those steps.

   <p>GPS is distributed with XML files describing the interfaces to
ClearCase, CVS and Subversion. These XML files are located in the directory
<code>share/gps/plug-ins</code> in the GPS installation, and can be used as a
reference for implementing new custom VCS interfaces.

   </body></html>