devel/p4 2026.1.3062361

Update devel/p4 to 2015.1/1314399

Approved by:	mat (mentor, implicit)
MFH:		2015Q4

Update devel/p4 to 2015.1/1252202 to accommodate micropatching.

Approved by:	mat (mentor, implicit)
MFH:		2015Q4

Mark BROKEN: checksum mismatch

Reported by:	pkg-fallout
MFH:		2015Q4

Update devel/p4 and devel/p4d to 2015.1/1227227

Approved by:	mat (mentor, implicit)
MFH:		2015Q3

Update devel/p4, devel/p4d, and devel/p4p to 2015.1/1227227.

Fixes micropatching update breakage.

Approved by:	mat (mentor, implicit)
MFH:		2015Q3

Accidentally forgot to remove the broken line.

Submitted by:	jkim@
MFH:		2015Q3

Update devel/p4* ports to 2015.1/1204891

Approved by:	erwin (mentor)
MFH:		2015Q3
Differential Revision:	https://reviews.freebsd.org/D3177

=> Attempting to fetch ftp://ftp.perforce.com/perforce/r15.1/bin.freebsd100x86_64/p4 fetch: ftp://ftp.perforce.com/perforce/r15.1/bin.freebsd100x86_64/p4: size mismatch: expected 2815472, actual 2815536

Sponsored by:	Absolight

Update to devel/p4 2015.1/1126382 to fix broken port. Migrate common variable for the devel/p4* ports into the Makefile.inc.

PR:		201216
Differential Revision:	https://reviews.freebsd.org/D3088
Approved by:	mat (mentor)
MFH:		2015Q3

Revert r391601 "- devel/p4: Unbreak"

I have to fix all the p4* ports too.
Teach me to fix something.

Pointyhat to: myself

- devel/p4: Unbreak

- Fix distinfo things

- Mark BROKEN: checksum mismatch

=> Attempting to fetch ftp://ftp.perforce.com/perforce/r14.2/bin.freebsd100x86_64/p4
fetch: ftp://ftp.perforce.com/perforce/r14.2/bin.freebsd100x86_64/p4: size mismatch: expected 2732720, actual 2755088
=> Attempting to fetch http://filehost.perforce.com/perforce/r14.2/bin.freebsd100x86_64/p4
fetch: http://filehost.perforce.com/perforce/r14.2/bin.freebsd100x86_64/p4: size mismatch: expected 2732720, actual 2755088

Approved by:	portmgr blanket
Reported by:	pkg-fallout

Update p4 to 2014.2/1045032

Approved by:	mentor (mat, implicit)
MFH:		2015Q2

Update to 2014.2/1033284 to fix checksum mismatch.

Approved by:	mentor (mat, implicit)
MFH:		2015Q2

Mark BROKEN: unfetchable

Reported by:	pkg-fallout

Remove OSVERSION checks that do not make sense any more.

For example (${OSVERSION} >= 900000 && ${OSVERSION} < 900021) is always true,
as is (${OSVERSION} > 900002 || ${OSVERSION} < 900000 && ${OSVERSION} > 800107).

Regarding patches, when an EXTRA_PATCHES is no longer needed, I remove it, when
it is always needed, I renamed it, in one case, I merged two patches.

Differential Revision:	https://reviews.freebsd.org/D2209

Update devel/p4 and devel/p4d to 2014.2.978861.

Differential Revision:	https://reviews.freebsd.org/D1449
Approved by:		erwin (mentor)
MFH:			2015Q1

devel/p4: Limit use to FreeBSD

Update Perforce related ports to 2014.2/962050. Fix typo in fallback URI on a couple of the ports.

Differential Revision:	https://reviews.freebsd.org/D1229
Approved by:		mat (mentor), erwin (mentor)
MFH:			2014Q4

Update Perforce ports to 2014.2.

p4 2014.2.943801
p4d 2014.2.935585
p4ftpd 2014.2.935585
p4p 2014.2.935585

Approved by:	mat (mentor)

- Update to the latest upstream versions:   - 2014.1 for p4, p4d, p4ftpd, p4p   - 2012.1 build update for 10.x releases

PR:		191648
Submitted by:	gordon (maintainer)
Approved by:	mentors (implicit)

Stage support

Add NO_STAGE all over the place in preparation for the staging support (cat: devel part 3)

Update p4 client to 2012.1/473528.

Prodded by: rpaulo

Update p4 to 2011.1/393975.

Update p4 client to 2011.1/389946

Upgrade Perforce related ports to 2011.1/370818. Of note is the loss of sparc64 and support for FreeBSD 5.x releases. Older versions of Perforce are still supported and those needing support for those platforms can download the last version at ftp://ftp.perforce.com/perforce/r10.2/

Submitted by:	gibbs@
Feature safe:	yes

Update p4 port to 2010.2/295040.

Update to new version of Perforce 2010.2/279478.

Deprecate md5 in favour of sha256 checksums.  md5 checksums will no longer be generated or checked, and will be silently ignored for now.  Also, generalize the MD5_FILE macro to DISTINFO_FILO.

PR:		149657
Submitted by:	rene
Approved by:	portmgr
Tested on:	pointyhat i386 7-exp

Update to new version of Perforce 2010.1/265509.

Update Perforce ports to 2010.1.

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)

p4 is the client part of the Perforce Control System. Update to 2009.2.238357

For the server-related parts, use devel/perforce

PR:		ports/145824
Submitted by:	gordon
Approved by:	tabthorpe (mentor)

Drop maintainership

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.txt
http://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)

  #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

Update distpaths.

Pointy hat to:	me

Fix logdir for package installation

Noted by:	droso

- 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

Add SHA256 checksum for alpha binaries

PR:		ports/118192
Submitted by:	Philip M. Gollucci <pgollucci@p6m7g8.com>

Missed two new distinfo files

- Update to 2007.3 - Also see: 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.
        This change prevents that from happening.  (Bug #26682).

    #136586 **
        In certain cases inconsistent results depending on depot
        path could be observed for some commands.  Typically when
        this happened an unrestricted 'p4 sync' would bring back
        correct behaviour.  This problem only occured when a file
        that had been previously synced was no longer mapped by the
        current client view and the client path name had a '.' in
        a significant position of its path.  This has been fixed
        (Bug #24943, #26541).

    #135236 **
        Unintegrated revisions prior to a delete could cause
        undesirable file re-branching in subsequent integrations.
        This change brings back an older behavior, which is to
        not re-branch from revisions prior to a delete when the
        target is also deleted. (Bug #25662)

For complete list of changes, see:

    http://www.perforce.com/perforce/doc.062/user/relnotes.txt

Chase updated binaries.

For complete list of changes, see:

    http://www.perforce.com/perforce/doc.061/user/relnotes.txt

Noticed by:	kris