CVS log for pkgsrc/devel/cvsutils/Makefile

Up to [cvs.NetBSD.org] / pkgsrc / devel / cvsutils

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

*: recursive bump for perl 5.36

*: recursive bump for perl 5.34

cvsutils: update to 0.2.6.

ChangeLog:

2013-05-31  Pavel Roskin  <[email protected]>

	* Version 0.2.6 released.

	* COPYING: New file, GPL v2, as suggested by Automake.

2013-05-11  Pavel Roskin  <[email protected]>

	* cvsu.pl (process_arg): Check for words "Result of merge"
	rather than for "+" to fing the results of merge.  In some
	cases, there is no "+" in the timestamp.
	Reported by Mikhail Gusarov <[email protected]>

*: bump PKGREVISION for perl-5.32.

Bump PKGREVISIONs for perl 5.30.0

Recursive bump for perl5-5.28.0

cvsutils: follow redirect

Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.

Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.

Bump for perl-5.20.0.
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.

Bump all packages for perl-5.18, that
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.

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

Remove unused doc installation target.

Import cvsutils-0.2.5; package originally created by
<[email protected]>.

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.)

Initial revision