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
|
Source: cvs
Section: vcs
Priority: optional
Maintainer: Thorsten Glaser <tg@mirbsd.de>
Homepage: http://www.nongnu.org/cvs/
Build-Depends: debhelper-compat (= 13),
ghostscript, groff, libbsd-dev, libkrb5-dev | heimdal-dev,
# # optional, for running the sanity suite
# procps,
texinfo, texlive-base, zlib1g-dev
Standards-Version: 4.5.1
Rules-Requires-Root: no
VCS-git: https://evolvis.org/anonscm/git/alioth/cvs.git -b master
VCS-Browser: https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=alioth/cvs.git;a=shortlog;h=refs/heads/master
Package: cvs
Architecture: any
Multi-Arch: foreign
Depends: ${misc:Depends}, ${shlibs:Depends}, adduser
Recommends: openssh-client
Suggests: mksh, rcs
Enhances: rcs, cvs2svn (>= 2.4.0-4~)
Description: Concurrent Versions System
CVS is a version control system, which allows you to keep access
to old versions of files (usually source code), keep a log of
who, when, and why changes occurred, etc., like RCS or SCCS.
It handles multiple developers, multiple directories, triggers to
enable/log/control various operations, and can work over a wide
area network. The texinfo manual provides further information on
more tasks that it can perform.
.
There are some tasks that are not covered by CVS. They can be done in
conjunction with CVS but will tend to require some script-writing and
software other than CVS. These tasks are bug-tracking, build management
(that is, make and make-like tools), and automated testing. However,
CVS makes these tasks easier.
.
This package contains a CVS binary which can act as both client and
server, although there is no CVS dæmon; to access remote repositories,
please use :extssh: not :pserver: any more.
|
