| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
1.22 (July 2018)
Add man pages.
Change license to 3-clause BSD.
Replace typedef unsigned char u_int8 etc with stdint.h types.
Update to new autotools.
Generate html versions from man pages.
Reflect the manpages in the homepage.
Fix recvmsg() on Solaris.
Detect clang for compiling.
Fix generating a rpm package.
Fix building on Windows.
|
|
|
|
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
|
|
|
|
|
|
------------------------------
1.21 (July 2016)
Yann E. MORIN (yann.morin.1998@free.fr): Buildroot [1] is a build-system
targetting embedded devices. It is able to build toolchains for various
architectures, based on the traditional GNU compiler collection gcc, the GNU
binutils and various C libraries, such as GNU libc (glibc), uClibc [2] [3] or
musl [4].
glibc is a feature-full C library, which has had support for Yellow Pages
(and the rest of the SUN RPC stuff) for a long time. However, circa the 2.14
release, glibc stopped installing the RPC headers [5], on the principle that
providing the RPC implementation would be better served by a third-party
package, namely ti-rpc [6]. That did not happen in time, so installing the
RPC headers from glibc was re-instated circa 2.16.
uClibc (no longer maintained, replaced by a fork, uClibc-ng) is a fully
configurable C library for embedded systems. It entirely lacks a SUN RPC
implementation altogether.
musl is standards-conforming, lightweight C library. It also entirely lacks a
SUN RPC implementation.
TI-RPC is a stand-alone package. It may or may not be available (because the
user may not need SUN RPC stuff on an embedded device, for example). Besides,
it is not yet as feature-full as the implementation in glibc, though for all
practical means, it is totally useable.
So, there are cases where a SUN RPC implementation is not available.
This patch makes it so that the use of Yellow Pages is conditional on the
presence of a SUN RPC implementation, by checking at ./configure whether the
required header is present, and disabling the corresponding code if the
header is missing.
At the same time, the legacy, long unsupported AM_C_PROTOTYPES directive is
also removed, as it makes recent-ish autoconf fail.
|
|
Existing SHA1 digests verified, all found to be the same on the
machine holding the existing distfiles (morden). Existing SHA1
digests retained for now as an audit trail.
|
|
1.20 (October 2013)
Nick Birch (Nick.Birch@s-and-t.com): rtpsend -l (loop) flag does
not work. Modified to rewind input file on feof if loop was
set. Fails if length of line is greater than 2048
characters. Increased to 4096 (sufficient for typical
rtpdump: Put space after ext_data=<hex extension data> so that it
can be parsed by rtpsend. parse_header doesn't comprehend the
possible extension header. As a consequence any extension header
data is also dumped twice. Once in the ext_data report and then a
second time in the data report. Modify parse_header to return hlen
that comprehends the extension header if present.
The format for reporting contributing sources does not match the
format accepted by rtpsend (i.e., reports "csrc[n] = xxxx" rather
than "csrc[n]=0xxxxx"). Fixed. Note: the documentation is less
than clear on the csrc syntax accepted by rtpsend.
1.19 (August 2010)
Krzysztof Burghardt (krzysztof@burghardt.pl): "Wireshark
implemented "rtpdump" file format in a bit different way, so
cooperation beetwen those program is a bit problematic.
Moreover rtptools compiled on i386 and amd64 have different size
of file header (size of long in timeval is different)."
|
|
|
|
|
|
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The rtptools distribution consists of a number of small applications that
can be used for processing RTP data.
|
