| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
as a directory name can't be attributed to a package
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Mirror the distfile on LOCAL as a http backup for clients that
can't use https. (Suggested by mat@)
Add MANPAGES option (default YES) because generating the man page
adds a significant number of build dependencies.
Add a comment explaining that the DOXYGEN=NO option gets ignored
if doxygen is installed.
Use option helpers (suggested by mat@).
Use PORTDOCS=* to avoid the need to change pkg-plist if doxygen
changes.
Use INSTALL_TARGET=install-strip instead of ${STRIP_CMD}
(suggested by marino@).
Simplify examples installation.
Differential Revision: https://reviews.freebsd.org/D1484
Approved by: mat (mentor)
Sponsored by: Farsight Security, Inc.
|
|
|
|
|
|
| |
PR: ports/196342
Submitted by: Naram Qashat (maintainer)
Exp-run and fixes to depending ports: self
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ChangeLog:
nmsg (0.9.1)
* Fix a crash that was caused by incorrect initialization of
ProtobufCBufferSimple objects.
* Increase the required verbosity level for several noisy debugging log
messages in the seqsrc tracking code from 5 (nmsgtool -ddddd) to 6
(nmsgtool -dddddd).
PR: 195696
Submitted by: maintainer
|
| |
|
|
|
|
|
|
|
|
|
|
| |
to GCC 4.8.3.
Part II, Bump PORTREVISIONs.
PR: 192025
Tested by: antoine (-exp runs)
Approved by: portmgr (implicit)
|
|
|
|
|
| |
PR: 192771
Submitted by: maintainer
|
|
|
|
|
| |
PR: 192695
Submitted by: maintainer
|
|
|
|
|
|
|
|
| |
Update dependent ports to build with it
Most of work by: pi@
Exp-run: self
PR: ports/190943
|
|
PR: 190601
Submitted by: Don Lewis (truckman@)
================================================================
The NMSG format is an efficient encoding of typed, structured data into
payloads which are packed into containers which can be transmitted over
the network or stored to disk. libnmsg is the reference implementation
of this format and provides an extensible interface for creating and
parsing messages in NMSG format. The NMSG format relies on Google
Protocol Buffers to encode the payload header. Individual NMSG payloads
are distinguished by assigned vendor ID and message type values and
libnmsg provides a modular interface for registering handlers for
specific message types. libnmsg makes it easy to build new message
types using the protobuf-c compiler.
|