pkgsrc/devel/cvs/Makefile

61 lines
1.5 KiB
Makefile
Raw Normal View History

Update to 1.11.20. NOTE: currently without IPv6 support, until there is an updated KAME patch for it. Changes: Changes since 1.11.19: ********************** SERVER SECURITY FIXES * Thanks to a report from Alen Zukich, several minor security issues have been addressed. One was a buffer overflow that is potentially serious but which may not be exploitable, assigned CAN-2005-0753 by the Common Vulnerabilities and Exposures Project <http://www.cve.mitre.org>. Other fixes resulting from Alen's report include repair of an arbitrary free with no known exploit and several plugged memory leaks and potentially freed NULL pointers which may have been exploitable for a denial of service attack. * Thanks to a report from Craig Monson, minor potential vulnerabilities in the contributed Perl scripts have been fixed. The confirmed vulnerability could allow the execution of arbitrary code on the CVS server, but only if a user already had commit access and if one of the contrib scripts was installed improperly, a condition which should have been quickly visible to any administrator. The complete description of the problem is here: <https://ccvs.cvshome.org/issues/show_bug.cgi?id=224>. If you were making use of any of the contributed trigger scripts on a CVS server, you should probably still replace them with the new versions, to be on the safe side. Unfortunately, our fix is incomplete. Taint-checking has been enabled in all the contributed Perl scripts intended to be run as trigger scripts, but no attempt has been made to ensure that they still run in taint mode. You will most likely have to tweak the scripts in some way to make them run. Please send any patches you find necessary back to <bug-cvs@gnu.org> so that we may again ship fully enabled scripts in the future. You should also make sure that any home-grown Perl scripts that you might have installed as CVS triggers also have taint-checking enabled. This can be done by adding `-T' on the scripts' #! lines. Please try running `perldoc perlsec' if you would like more information on general Perl security and taint-checking. BUG FIXES * Thanks to a report and a patch from Georg Scwharz CVS now builds without error on IRIX 5.3 DEVELOPER ISSUES * We've standardized on Automake 1.9.5 to get some at new features that make our jobs easier. See the HACKING file for more on using the autotools with CVS.
2005-04-19 14:39:18 +02:00
# $NetBSD: Makefile,v 1.84 2005/04/19 12:39:18 wiz Exp $
#
Update to 1.11.20. NOTE: currently without IPv6 support, until there is an updated KAME patch for it. Changes: Changes since 1.11.19: ********************** SERVER SECURITY FIXES * Thanks to a report from Alen Zukich, several minor security issues have been addressed. One was a buffer overflow that is potentially serious but which may not be exploitable, assigned CAN-2005-0753 by the Common Vulnerabilities and Exposures Project <http://www.cve.mitre.org>. Other fixes resulting from Alen's report include repair of an arbitrary free with no known exploit and several plugged memory leaks and potentially freed NULL pointers which may have been exploitable for a denial of service attack. * Thanks to a report from Craig Monson, minor potential vulnerabilities in the contributed Perl scripts have been fixed. The confirmed vulnerability could allow the execution of arbitrary code on the CVS server, but only if a user already had commit access and if one of the contrib scripts was installed improperly, a condition which should have been quickly visible to any administrator. The complete description of the problem is here: <https://ccvs.cvshome.org/issues/show_bug.cgi?id=224>. If you were making use of any of the contributed trigger scripts on a CVS server, you should probably still replace them with the new versions, to be on the safe side. Unfortunately, our fix is incomplete. Taint-checking has been enabled in all the contributed Perl scripts intended to be run as trigger scripts, but no attempt has been made to ensure that they still run in taint mode. You will most likely have to tweak the scripts in some way to make them run. Please send any patches you find necessary back to <bug-cvs@gnu.org> so that we may again ship fully enabled scripts in the future. You should also make sure that any home-grown Perl scripts that you might have installed as CVS triggers also have taint-checking enabled. This can be done by adding `-T' on the scripts' #! lines. Please try running `perldoc perlsec' if you would like more information on general Perl security and taint-checking. BUG FIXES * Thanks to a report and a patch from Georg Scwharz CVS now builds without error on IRIX 5.3 DEVELOPER ISSUES * We've standardized on Automake 1.9.5 to get some at new features that make our jobs easier. See the HACKING file for more on using the autotools with CVS.
2005-04-19 14:39:18 +02:00
DISTNAME= cvs-1.11.20
CATEGORIES= devel
# (SSL) download URL according to http://www.cvshome.org/ is
Update to 1.11.20. NOTE: currently without IPv6 support, until there is an updated KAME patch for it. Changes: Changes since 1.11.19: ********************** SERVER SECURITY FIXES * Thanks to a report from Alen Zukich, several minor security issues have been addressed. One was a buffer overflow that is potentially serious but which may not be exploitable, assigned CAN-2005-0753 by the Common Vulnerabilities and Exposures Project <http://www.cve.mitre.org>. Other fixes resulting from Alen's report include repair of an arbitrary free with no known exploit and several plugged memory leaks and potentially freed NULL pointers which may have been exploitable for a denial of service attack. * Thanks to a report from Craig Monson, minor potential vulnerabilities in the contributed Perl scripts have been fixed. The confirmed vulnerability could allow the execution of arbitrary code on the CVS server, but only if a user already had commit access and if one of the contrib scripts was installed improperly, a condition which should have been quickly visible to any administrator. The complete description of the problem is here: <https://ccvs.cvshome.org/issues/show_bug.cgi?id=224>. If you were making use of any of the contributed trigger scripts on a CVS server, you should probably still replace them with the new versions, to be on the safe side. Unfortunately, our fix is incomplete. Taint-checking has been enabled in all the contributed Perl scripts intended to be run as trigger scripts, but no attempt has been made to ensure that they still run in taint mode. You will most likely have to tweak the scripts in some way to make them run. Please send any patches you find necessary back to <bug-cvs@gnu.org> so that we may again ship fully enabled scripts in the future. You should also make sure that any home-grown Perl scripts that you might have installed as CVS triggers also have taint-checking enabled. This can be done by adding `-T' on the scripts' #! lines. Please try running `perldoc perlsec' if you would like more information on general Perl security and taint-checking. BUG FIXES * Thanks to a report and a patch from Georg Scwharz CVS now builds without error on IRIX 5.3 DEVELOPER ISSUES * We've standardized on Automake 1.9.5 to get some at new features that make our jobs easier. See the HACKING file for more on using the autotools with CVS.
2005-04-19 14:39:18 +02:00
# https://ccvs.cvshome.org/files/documents/19/861/cvs-1.11.20.tar.bz2
MASTER_SITES= ${MASTER_SITE_BACKUP}
EXTRACT_SUFX= .tar.bz2
MAINTAINER= wiz@NetBSD.org
2000-05-21 17:27:29 +02:00
HOMEPAGE= http://www.cvshome.org/
COMMENT= Concurrent Versions System
2004-01-05 12:42:20 +01:00
PKG_INSTALLATION_TYPES= overwrite pkgviews
GNU_CONFIGURE= yes
.include "../../mk/bsd.prefs.mk"
BUILD_DEFS+= USE_INET6
2001-04-13 07:33:16 +02:00
.if defined(USE_INET6) && !empty(USE_INET6:M[yY][eE][sS]) && \
2004-01-21 15:14:13 +01:00
empty(MACHINE_PLATFORM:MSunOS-5.[89]-*) && \
empty(MACHINE_PLATFORM:MSunOS-5.10-*) && \
Update to 1.11.20. NOTE: currently without IPv6 support, until there is an updated KAME patch for it. Changes: Changes since 1.11.19: ********************** SERVER SECURITY FIXES * Thanks to a report from Alen Zukich, several minor security issues have been addressed. One was a buffer overflow that is potentially serious but which may not be exploitable, assigned CAN-2005-0753 by the Common Vulnerabilities and Exposures Project <http://www.cve.mitre.org>. Other fixes resulting from Alen's report include repair of an arbitrary free with no known exploit and several plugged memory leaks and potentially freed NULL pointers which may have been exploitable for a denial of service attack. * Thanks to a report from Craig Monson, minor potential vulnerabilities in the contributed Perl scripts have been fixed. The confirmed vulnerability could allow the execution of arbitrary code on the CVS server, but only if a user already had commit access and if one of the contrib scripts was installed improperly, a condition which should have been quickly visible to any administrator. The complete description of the problem is here: <https://ccvs.cvshome.org/issues/show_bug.cgi?id=224>. If you were making use of any of the contributed trigger scripts on a CVS server, you should probably still replace them with the new versions, to be on the safe side. Unfortunately, our fix is incomplete. Taint-checking has been enabled in all the contributed Perl scripts intended to be run as trigger scripts, but no attempt has been made to ensure that they still run in taint mode. You will most likely have to tweak the scripts in some way to make them run. Please send any patches you find necessary back to <bug-cvs@gnu.org> so that we may again ship fully enabled scripts in the future. You should also make sure that any home-grown Perl scripts that you might have installed as CVS triggers also have taint-checking enabled. This can be done by adding `-T' on the scripts' #! lines. Please try running `perldoc perlsec' if you would like more information on general Perl security and taint-checking. BUG FIXES * Thanks to a report and a patch from Georg Scwharz CVS now builds without error on IRIX 5.3 DEVELOPER ISSUES * We've standardized on Automake 1.9.5 to get some at new features that make our jobs easier. See the HACKING file for more on using the autotools with CVS.
2005-04-19 14:39:18 +02:00
empty(MACHINE_PLATFORM:MLinux-*) && \
defined(NOT_YET_AVAILABLE_FOR_CVS_1_11_20)
CONFIGURE_ARGS+= --enable-ipv6
Update cvs to 1.11.2. Changes: Changes since 1.11.1p1: * The "log" and "rlog" commands now have a -S option to suppress the header information when no revisions are selected. * A serious error that allowed read-only users to tag files has been corrected. * The "annotate" command will no longer annotate binary files unless you specify the new -F option. * The "tag" and "rtag" commands will no longer move or delete branch tags unless you use the new -B option. (This prevents accidental changes to branch tags that are hard to undo.) * We've standardized on the 1.5 Automake release for the moment. Again, this should only really affect developers. See the section of the INSTALL file about using the autotools if you are compiling CVS yourself. Changes from 1.11.1 to 1.11.1p1: * Read only access was broken - now fixed. Changes from 1.11 to 1.11.1: * The "cvs diff" command now accepts the -y/--side=by-side and -T/ --initial-tab options. (To use these options with a remote repository, both the client and the server must support them.) * The expansion of the loginfo format string has changed slightly. Previously, the expansion was surrounded by single quotes ('); if a file name contained a single quote character, the string would not be parsed as a single entity by the Unix shell (and it would not be possible to parse it unambiguously). Now the expansion is surrounded by double quotes (") and any embedded dollar signs ($), backticks (`), backslashes (\), and double quotes are preceded by a backslash. This is parsed as a single entity by the shell reguardless of content. This change should not be noticable unless you're not using a Unix shell or you have embedded the format string inside a double quoted string. * There was a bug in the diff code which sometimes caused conflicts to be flagged which shouldn't have been. This has been fixed. * New "cvs rlog" and "cvs rannotate" commands have been added to get log messages and annotations without having to have a checked-out copy. * Exclusive revision ranges have been added to "cvs log" using :: (similar to "cvs admin -o"). * The VMS client now accepts wildcards if you're running VMS 7.x. * ZLIB has been updated to version 1.1.3, the most current version. This includes mostly some optimizations and minor bug fixes. * The ~/.cvspass file has a slightly modified format. CVSROOTs are now stored in a new canonical form - hostnames are now case insensitive and port numbers are always stored in the new format. Until a new login for a particular CVSROOT is performed with the new version of CVS, new and old versions of CVS should interoperate invisibly. After that point, an extra login using the old version of CVS may be necessary to continue to allow the new and old versions of CVS to interoperate using the same ~/.cvspass file and CVSROOT. The exception to this rule occurs when the CVSROOTs used with the different versions use case insensitively different hostnames, for example, "empress", and "empress.2-wit.com". * A password and a port number may now be specified in CVSROOT for pserver connections. The new format is: :pserver:[[user][:password]@]host[:[port]]/path Note that passwords specified in a checkout command will be saved in the clear in the CVS/Root file in each created directory, so this is not recommended, except perhaps when accessing anonymous repositories or the like. * The distribution has been converted to use Automake. This shouldn't affect most users except to ease some portability concerns, but if you are building from the repository and encounter problems with the makefiles, you might try running ./noautomake.sh after a fresh update -AC.
2002-11-24 22:31:20 +01:00
PATCH_SITES= ftp://ftp.kame.net/pub/kame/misc/
Update to 1.11.19. pkgsrc change: patch-ag, provided by Georg Schwarz, added to fix the build on IRIX. NEWS: Changes since 1.11.18: ********************** BUG FIXES * An intermittant assertion failure in checkout has been fixed. * Thanks to a report from Chris Bohn, all the source files needed for the Windows "red file" fix are actually included in the distribution. * Misc bug and documentation fixes. Changes from 1.11.17 to 1.11.18: ******************************** BUG FIXES * Thanks to a report from Gottfried Ganssauge, CVS no longer exits when it encounters links pointing to paths containing more than 128 characters. * Thanks to a report from Dan Peterson, error messages from GSSAPI servers are no longer truncated. * Thanks to a report from Dan Peterson, attempts to resurrect a file on the trunk that was added on a branch no longer causes an assertion failure. * Thanks to a report from Dan Peterson, imports to branches like "1.1." no longer create corrupt RCS archives. * Thanks to a report from Chris Bohn, links from J.C. Hamlin, and code posted by Jonathan Gilligan, we think we have finally corrected the Windows "red-file" (daylight savings time) bug once and for all. * Thanks to a patch from Jeroen Ruigrok/asmodai, the log_accum.pl script should no longer elicit warnings from Perl 5.8.5. * The r* commands (rlog, rls, etc.) can once again handle requests to run against the entire repository (e.g. `cvs rlog .'). Thanks go to Dan Peterson for the report. * A problem where the attempted access of files via tags beginning with spaces could cause the CVS server to hang has been fixed. This was a particular problem with WinCVS clients because users would sometimes accidentally include spaces in tags pasted into a dialog box. This fix also altered some of the error messages generated by the use of invalid tags. Thanks go to Dan Peterson for the report. * Thanks to James E Wilson for a bug fix to modules processing "gcc-core -a !gcc/f gcc" will no longer exclude gcc/fortran by mistake. * Thanks to Conrad Pino, the Windows build works once again. * Misc updates to the manual. DEVELOPER ISSUES * We've standardized on Automake 1.9.3 to get some at new features that make our jobs easier. See the note below on the Autoconf upgrade for more details. * We've standardized on Autoconf version 2.59 to get presumed bug fixes and features, but nothing specific. Mostly, once we decide to upgrade one of the autotools we just figure it'll save time later to grab the most current versions of the others too. See the HACKING file for more on using the autotools with CVS.
2005-03-01 16:36:48 +01:00
PATCHFILES= cvs-1.11.19-v6-20050205.diff.gz
PATCH_DIST_STRIP= -p1
.else
CONFIGURE_ARGS+= --disable-ipv6
.endif
.if defined(KERBEROS)
. include "../../mk/krb5.buildlink3.mk"
CONFIGURE_ARGS+= --enable-encryption
CONFIGURE_ARGS+= --with-gssapi=${KRB5BASE}
CONFIGURE_ARGS+= --with-krb4=${KRB5BASE}
. if ${OPSYS} == "Darwin"
LDFLAGS+= -framework Kerberos
. endif
.else
CONFIGURE_ARGS+= --without-gssapi
.endif
1998-08-21 21:06:51 +02:00
.if defined(RCS_LOCALID)
pre-fetch:
2000-10-22 00:21:23 +02:00
@${ECHO} RCS_LOCALID is now replaced by the tag variable in CVSROOT/config.
1998-08-21 21:06:51 +02:00
.endif
CONFIGURE_ENV+= perl_path=${PERL5}
1998-08-21 21:06:51 +02:00
INFO_FILES= cvs.info cvsclient.info
USE_MAKEINFO= yes
TEXINFO_REQD?= 4.0
2004-01-05 12:42:20 +01:00
.include "../../devel/zlib/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"