kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/cvsutils/Makefile

19 lines
421 B
Makefile
Raw Normal View History

Bump PKGREVISIONs for perl 5.30.0
2019-08-11 15:17:48 +02:00
# $NetBSD: Makefile,v 1.11 2019/08/11 13:18:41 wiz Exp $
Import cvsutils-0.2.5; package originally created by <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.)
2008-09-11 07:01:08 +02:00
DISTNAME= cvsutils-0.2.5
Bump PKGREVISIONs for perl 5.30.0
2019-08-11 15:17:48 +02:00
PKGREVISION= 7
Import cvsutils-0.2.5; package originally created by <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.)
2008-09-11 07:01:08 +02:00
CATEGORIES= devel
MASTER_SITES= http://www.red-bean.com/cvsutils/releases/
MAINTAINER= pkgsrc-users@NetBSD.org
cvsutils: follow redirect
2018-02-11 16:39:38 +01:00
HOMEPAGE= https://www.red-bean.com/cvsutils/
Import cvsutils-0.2.5; package originally created by <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.)
2008-09-11 07:01:08 +02:00
COMMENT= CVS utilities to facilitate working
GNU_CONFIGURE= yes
USE_TOOLS+= perl:run
REPLACE_PERL= *.pl
REPLACE_SH= *.sh
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink