This is the C client library for Couchbase. It communicates with the cluster
and speaks the relevant protocols necessary to connect to the cluster and
execute data operations.
all: drop support for FreeBSD 13, mips and risc64sf
Reviewed by: many (*)
Differential Revision: https://reviews.freebsd.org/D55624
Differential Revision: https://reviews.freebsd.org/D55642 (merged in from bofh)
many (*)
acm arrowd brooks cmt dch decke dinoex eduardo fluffy fuz gahr garga
jbeich joerg jrm kai kenrap martymac matthew mfechner michaelo mizhka
nobutaka pkubaj se tagattie thj
Anton Saietskii
GenericRikka
Gert Doering
Jan Bramkamp
Oleh Hushchenkov
Oleksandr Kryvulia
Ralf van der Enden
Yamagi
desktop kde python tcltk office
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 )
Fix CONFLICTS entries of multiple ports
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
(Only the first 15 lines of the commit message are shown above )
Use the most recent change from arm to fix build on riscv64.
While here, generalize the arm expression the way we usually do.
Approved by: portmgr (tier-2 blanket)
Mark broken on armvX: tries and fails to link with dtrace. This could
probably be fixed via a configuration knob as in databases/memcached.
While here, pet portlint.
Approved by: portmgr (tier-2 blanket)
databases/libcouchbase: tentatively attempt to unbreak parallel builds.
The problem was not immediately obvious to me: after eliminating dtrace(1)
output filename clash and forcibly serializing two normally concurrent in
parallel mode linking stages, the problem did not go away. In fact, while
the port was building seemingly fine in a single-thread (unsafe) mode, the
messages "No probe sites found for declared provider" were still sometimes
present in the log, as well as "target object (...) already exists. Please
remove the target object and rebuild all the source objects if you wish to
run the DTrace".
Running dtrace(1) via truss(1) revealed something odd: it was opening the
substrate object files in read-write mode! Further tests and studying its
code (/usr/src/cddl/contrib/opensolaris/lib/libdtrace/common/dt_link.c;
see process_obj() and dt_modtext() functions) had confirmed that it is not
(Only the first 15 lines of the commit message are shown above )
Remove MAKE_JOBS_UNSAFE marker: it was added as part of r421281 upon the
port's inception as of version 2.6.2, however, it was neither present in
submitted PR nor explained in the original commit log by pi@. So far my
quick tests do not show evidence that it is parallel-build unsafe.
We'll ask for forgiveness if it is indeed broken against -j X builds and
reinstate MAKE_JOBS_UNSAFE, but with a proper explanation this time.
While here, remove needless += from CMAKE_ARGS and place them at a better
location within the Makefile.
PR: 205377
