Perforce is a commercial revision control system that can be used
gratis for developing free software. (see the WWW page for details).
WWW: http://www.perforce.com/
Remove old devel/perforce
The server parts are now in devel/p4d, devel/p4p, devel/p4ftpd, and devel/p4web
PR: ports/145824
Submitted by: gordon
Approved by: tabthorpe (mentor)
Updated p4d. Bugs fixed:
#189734 **
The new tcp buffer calculation could cause a deadlock in
client/server communications. This problem was only detected
on configurations involving Solaris or Linux. Due to the
complications of platform specific tcp implementations the
algorithm has been reworked to make allowances for certain
eccentricities. (Bug #32494).
#188676 *
'p4 resolve' using the automatic option could crash the client
application when running on windows. This would only happen
if the 'theirs' file had been locked by another windows
application e.g. microsoft word. (Bug #32384)
Updated p4web. Bugs fixed:
#190006
Always offer browse depot selection in multiuser mode. (Bug #32704)
Complete release notes at:
http://www.perforce.com/perforce/doc.082/user/relnotes.txthttp://www.perforce.com/perforce/doc.082/user/p4webnotes.html
Updated p4web. Bugs fixed:
#186658
Fix problem with line numbers being skipped when viewing a file.
(Bug #031832)
#185786
P4Web no longer requires a client in browse only mode. (Bug #032227)
Complete release notes for p4web at:
http://www.perforce.com/perforce/doc.current/user/p4webnotes.html
Bugs fixed (from release notes):
#188676 *
'p4 resolve' using the automatic option could crash the client
application when running on windows. This would only happen
if the 'theirs' file had been locked by another windows
application e.g. microsoft word. (Bug #32384)
#188603 **
A user with a complicated view map could crash the server
by creating a spec using '-i' or editing a spec to use
a name which contains '%%<somenumber>'. This has
been fixed. (Bug #31933)
Noted by: pointyhat via pav
Bugs fixed (from release notes):
#179182 **
'p4 sync -p' via the proxy did not transfer files which
were not in the proxy's cache. Fixed. (Bug #31775)
#184476 **
Excessive wildcard use in client views could crash the
ntx64/p4d server under circumstances that would be handled
correctly by the ntx86/p4d server. It was discovered
that the 64-bit version of the windows server requires more
stack space to perform commands involving excessive wildcard
usage in client mappings. This has been resolved so that the
ntx6/p4d process behaves similarly to the ntx86/p4d.
(Bug #31737)
(Only the first 15 lines of the commit message are shown above )
- Update to 08.2
- Drop alpha support
- Fix log dir location [1]
- Fix depot permissions [1]
- Separate DIST_SUBDIR [2]
Submitted by: Bernard Treves Brown [1], infofarmer [2]
Bugs fixed (from release notes):
#152382 **
Sometimes 'p4 integrate' would find a distant base when
cherry picking revisions to integrate. Now 'p4 integrate'
insists that the base be the revision before the first
revision being integrated when cherry picking revisions.
(Bug #29016).
#152296 **
'p4 submit' could report "No files to submit" if the
combination of client mapped files and protections table
exceeded an internal limit. This limit was incorrectly
reached on case-insensitive Servers (Windows) by repeated
values in a generated map. This has been fixed. (Bug #28853)
Bugs fixed (from release notes):
#149704 **
'p4 integrate' could skip integrations in the face of
large branch views coupled with large protection tables.
This has been corrected. (Bug #28659)
#149538 **
'p4 integrate' could report "no permission on file(s)" if
the protections managed by 'p4 protect' had excessive wildcards
(too many ...'s in too many entries). Now 'p4 integrate'
should be no more sensitive than other commands to the number
of wildcards in protections, and in any event should fail
with a more appropriate message ("too may wildcards").
(Bug #28422).
Changes: http://www.perforce.com/perforce/doc.073/user/relnotes.txt
Chase updated binaries.
Bugs fixed: (from release notes):
#136755 **
A perforce server could shutdown with the message
"License expired" even when a new license with a valid
expire date was put in place (either manually or with
the 'p4 license' command). This only happened if the
license that the server was originally started with
became out of date. (Bug #24800)
#136742 **
'p4 obliterate' under certain conditions could purge an
archive file which still had lazy copies pointing to it.
(Only the first 15 lines of the commit message are shown above )
Chase updated binaries.
Bugs fixed: (from release notes):
#129932 **
'p4 submit' could fail when 'p4 integrate' mistakenly
attempts to branch from a deleted revision if that
source file was readded and that readded revision was
ignored into the target file. Fixed. (Bug #24663)
#128837 **
The server no longer exits after 10 consecutive attempts
to accept an incoming connection. Usually the reason for
this is that the computer is under configured and its
simply a server resource problem. In some cases the
problem can be on the client end, because of this the
server now sleeps, then continues to retry. (Bug #24156).
For complete list of changes, see:
http://www.perforce.com/perforce/doc.061/user/relnotes.txt
Noticed by: pavmail
Chase updated binaries.
Bugs fixed: (from release notes)
#114840 **
CPU usage has been reduced for 'p4 integrate' when it is
handling indirect integrations through a large number of
branches (hundreds or more). (Bug #23592).
For complete list of changes, see:
http://www.perforce.com/perforce/doc.061/user/relnotes.txt
Noticed by: "Stefan Schablowski" <stefan.schablowski@prolificx.com>
Chase updated binaries.
Bugs fixed (from release notes):
#113339 **
'p4 opened -a //...' was being adversely affected by
the optimization in change #109212. It is now back to
its previous performance. (Bug #23307)
#113270 **
Files changed from type ktext to text would be stored
at the server with the keywords unexpanded even if the
files had been submitted with the keywords expanded.
This behavior, present only in release 2006.1, has been
fixed. (Bug #23258)
(Only the first 15 lines of the commit message are shown above )
- Add dummy version number for unsupported platforms, to silence a warning
about malformed version string when processing INDEX
PR: ports/67920
Submitted by: Conrad J. Sabatier <conrads@cox.net>
Approved by: David Marshall <marshall@chezmarshall.com> (maintainer)
Updated i386 binaries for version 03.2.
PR: ports/64447
Submitted by: david marshall <marshall@chezmarshall.com> (maintainer)
Committed at: Exit of Chuou Highway in Japan
Update the distinfo checksums as a new version of Perforce is out in the wild.
Split distinfo into separate files for i386 and alpha architectures.
Submitted by: Steve Borrett <support@perforce.com>
Update the distinfo checksums as a new version of Perforce is out in the wild.
Split distinfo into separate files for i386 and alpha architectures.
Submitted by: Steve Borrett <support@perforce.com>
update to new perforce binaries
Perforce has released new binaries.
Also, with the popularity of portupgrade rising, I made some
(somewhat bogus) changes to the makefile to help pkg_version and
portupgrade figure out when the port has been upgraded.
I have moved the kludge on the PR to below the maintainer section.
PR: ports/56497
Submitted by: david marshall <marshall@chezmarshall.com>
Use IGNORE, not .error, on unsupported platforms. This should solve the
last remaining 'make readmes' problem on sparc64.
Reviewed by: petef
Approved by: David Marshall <marshall@chezmarshall.com> (MAINTAINER)
Remove FORBIDDEN, I have confirmed the updated checksum on the p4d
binary with Perforce support.
Thanks to: "Michael D. Shields" <mshields@perforce.com>
Use ${ECHO_CMD} instead of ${ECHO} where you mean the echo command; the ECHO
macro is set to "echo" by default, but it is set to "true" if make(1) is
invoked with the -s option while ECHO_CMD is always set to the echo command.
- Update to version 01.1 - Support the alpha platform (although it is still at
version 99.1) - Install p4ftpd - Create a non-privileged user and run p4d as
the user - Dig directories and make the port plug-and-play - Change the
configuration file's name to perforce.conf - Do not unconditionally remove
perforce.conf on deinstall - Make almost all parameters (including directory
layouts and user/group names) configurable via make variables - Make the
startup script support "restart" - Take over the maintainership
Add perforce, a well-done commercial source code control system. The
submitter tried to bundle an elisp script with this port, but I left it out
because it could just as well be put in a different port.
