Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
<pancake@phreaker.net>.
CVS Utilities is a set of scripts that operate on working directories of
CVS (Concurrent Versions System).
Unlike some other version control systems, it's common for CVS
repository to reside on a remote system. Unfortunately, the standard
CVS client requires connection to the repository for almost all
operations. This means that some operations are impossible when the
repository is unreachable over the network, or when the network
connection is slow compared to the size of the project.
In fact, CVS keeps some data in the working directory that allows for
some disconnected operations. In particular, no connection to the
repository is required to identify locally modified files. But the CVS
client cannot do it. This is the gap CVS Utilities aim to close.
Admittedly, the insistence of the CVS client on repository connection
can be justified in most cases. That's why CVS Utilities are not aiming
to be a "better client". It's an extension to CVS client with limited
capabilities but higher speed. (If someone was to write a better CVS
client, it would probably keep base versions or their checksums
somewhere, like Subversion does, but CVS Utilities use the same format
of the working directory as the standard CVS client.)
