The Perforce Client API is a simple beast which packages up the
command invocation, sends it to the server, and then acts on
instructions from the server to carry out the actual command.
For documentation: https://www.perforce.com/manuals/p4api/Content/P4API/Home-p4api.html
===> The following configuration options are available for p4api-2026.1.3062361:
EXAMPLES=on: Build and/or install examples
===> Use 'make config' to modify these settings
devel/{p4,p4api}: Unbreak build on arm
Also change devel/p4api to use devel/p4 files/patches and distinfo.
PR: 270531
Approved by: antonfb@hesiod.org (maintainer)
devel/p4: Update to r22.2.2407422
Remove BROKEN lines (this version is 7 years newer).
Documentation is only in html form online now.
PR: 270420
Approved by: antonfb@hesiod.org (maintainer)
devel/{p4,p4api}: relinquish maintainership
I haven't used these ports for 5 years, and I cannot test changes to
them.
PR: 270245
Approved by: fernape (ports)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel/p4 devel/p4api: cache distfiles in LOCAL
Perforce unhelpfully rebuilds their distfiles every few hours, changing the
archived files' timestamps in the process. This obviously changes their
checksums. Work around the issue by caching local copies of the distfiles and
using those for the checksums.
Also, set a sane DIST_SUBDIR since the distfiles are ambiguously named.
Also, take over maintainership from gordon.
Reported by: gordon, antoine
Reviewed by: mat
Approved by: mat (ports)
Sponsored by: Spectra Logic Corp
Differential Revision: https://reviews.freebsd.org/D14211
devel/p4 devel/p4api: build from source
Build devel/p4 and devel/p4api from source rather than use the prebuilt
binary downloads. This fixes p4api on FreeBSD 12. The ports originally used
the binaries because source wasn't available until a few years ago. By
happy accident, building from source also makes the ports available on
non-Intel architectures.
PR: 225613
Reviewed by: brd
Approved by: brd (ports)
Sponsored by: Spectra Logic Corp
Differential Revision: https://reviews.freebsd.org/D14162
remove RESTRICTED from devel/p4 and devel/p4api
devel/p4 and devel/p4api are BSD licensed, even though the distfile does not
include any license file. The source for these ports is separately
distributed through swarm.workshop.perforce.com, and Perforce support
assures me that the license found in the source also applies to the binary
distfile used by these ports.
PR: 215662
Reviewed by: mat, gordon
Approved by: mat (ports)
Sponsored by: Spectra Logic Corp
Differential Revision: https://reviews.freebsd.org/D8623
Update Perforce related ports due to micropatching.
Approved by: mat (mentor, implicit)
MFH: 2016Q3
Differential Revision: https://reviews.freebsd.org/D7220
Take over p4api port and update to recentish version 2014.2/978861.
Differential Revision: https://reviews.freebsd.org/D2029
Approved by: kuriyama, mat (mentor)
Add OPTIONS_DEFINE=DOCS for ports with %%PORTDOCS%% in the plist.
Where possible, correct a few instances where PORTDOCS was being used
to flag stuff in EXAMPLESDIR. For some ports, mostly those owned by
ruby@, PORTDOCS is applied to pretty much everything whether it's
documentation or example.
This port was not really usable on i386-5.X due to an updated GCC,
since C++ name mangling has changed in an incompatible way. Now that
perforce has put FreeBSD 5.X p4api binary on their FTP site, the port
can be updated to work on both 4.X and 5.X.
The tarball for 4.X was tested with 2.95.4. The tarball for 5.X was
tested with 3.3.1. If there were other incompatible name mangling
changes in GCC in between, neither will work, so beware.
Also, the FreeBSD 4.X p4api tarball checksum has changed. Perforce has
confirmed that the new checksum is correct.
Approved by: maintainer
