mandoc —
UNIX manpage compiler — anonymous CVS
Public access to the mandoc source code repository
Copies of the mandoc source code repository
and of a few other repositories of bsd.lv
software are available publicly for anonymous CVS access.
How not to use anonymous CVS
Most people using mandoc will not need
this service, and using it will merely complicate matters for no
gain. In particular, do not use anonymous CVS for any of the
following purposes:
- You merely want to use mandoc to read
your manuals, to search for manuals, to check manual source
code for correctness, to translate mdoc(7) code to man(7) code,
or to create HTML, PostScript, or PDF files. Do not use anonymous
CVS, use the version of mandoc that
comes with your operation system, or
if that doesn't exist or is too old for your purposes, use the
latest release.
- You merely want to briefly look up some current code in a
source file, or the historic development of one file or a few
files. Using the CVS
web interface is probably simpler than anonymous CVS
access.
- You maintain a port or package of mandoc
for an operating system. Never create a port or package from
a CVS checkout. Use the latest release.
How to use anonymous CVS
Anonymous CVS access is helpful in the following situations:
- You want to develop and submit
patches.
- You care about mandoc development
and want to run bleeding edge code for testing purposes. At
most times, CVS HEAD is a very good and stable version of mandoc
- but sometimes, during phases of particularly active development,
it may temporarily become less stable and more buggy than
released code. So running it is not recommended unless you
actively watch development and feel prepared to deal with bugs
that may creep in. If you experience problems running CVS HEAD,
please do report these problems,
mentioning that you run CVS HEAD. Running CVS HEAD and reporting
bugs is a great way to help the developers, actually.
- You are an operating system developer with commit access
to an operating system including mandoc
in the base system and want to integrate recent changes that
have not yet been released. This may occasionally be useful
for important bugfixes, and sometimes even for new features.
For example, the mandoc version in OpenBSD is usually in sync
with the CVS HEAD and not with the latest release. However,
there are exceptions when the CVS HEAD is temporarily unstable,
so you need to know what you are doing.
How to check out from anonymous CVS
To access the public copy of the repository, you need working
installations of CVS client
software and SSH client
software.
If your operating system has sane default settings, the following
command ought to be sufficient to create a CVS checkout into the
subdirectory mandoc of the current working directory:
$ cvs -d anoncvs@mandoc.bsd.lv:/cvs co mandoc
On some systems, the above command might fail with an error
similar to "connection refused" if your system attempts to open
an unencrypted connection using the obsolete RSH or :pserver:
protocols. In that case, it is necessary to explicitly specify
that you want to use SSH, as follows:
$ export CVS_RSH=ssh
$ cvs -d :ext:anoncvs@mandoc.bsd.lv:/cvs co mandoc
For more details on what anonymous CVS is and how it works, see
the OpenBSD page on
anonymous CVS. Only part of what is explained there applies
to the mandoc repository, though. For general help on CVS, see
the GNU info(1) manual on CVS.
Finally, note that the public repository is a copy, not the
master repository. It is usually updated after every commit,
but it may occasionally lag for a few minutes.
Repositories on this server
In addition to the mandoc source code
module, the following modules are available on this server:
In the commands listed above, just replace the word
mandoc with the name of the desired module.