ports/devel/p4d/Makefile, branch release/8.0.0

This commit was manufactured by cvs2svn to create tag 'RELEASE_8_0_0'.

2009-11-14T12:33:33Z

Updated p4d. Bugs fixed:

2009-03-24T08:32:40Z

#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.txt http://www.perforce.com/perforce/doc.082/user/p4webnotes.html

Updated p4web. Bugs fixed:

2009-02-25T07:26:57Z

#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):

2009-02-22T13:58:34Z

#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 '%%'. This has been fixed. (Bug #31933) Noted by: pointyhat via pav

Bugs fixed (from release notes):

2009-01-23T16:21:16Z

#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) #181214 ** 'p4 fstat -F' with a filter that contains a not (^) crashes the Perforce server. This has been fixed. (Bug #31771) #183252 ** A failure to open a temporary file during submit of a compressed file could lead to a server crash. This problem could occur on a windows server only. Fixed. (Bug #31952) #168144 * Shell wildcard expansion on Windows can once again be disabled by double quoting arguments. (Bug #30753)

- Remove conditional checks for FreeBSD 5.x and older

2009-01-05T19:44:02Z

Fix logdir for package installation

2009-01-02T20:43:25Z

Noted by: droso

- Update to 08.2

2008-12-29T14:38:38Z

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

2008-04-27T12:47:50Z

#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):

2008-04-10T08:29:47Z

#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