pkglint --only "https instead of http" -r -F
With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.
This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
Unsorted entries in PLIST files have generated a pkglint warning for at
least 12 years. Somewhat more recently, pkglint has learned to sort
PLIST files automatically. Since pkglint 5.4.23, the sorting is only
done in obvious, simple cases. These have been applied by running:
pkglint -Cnone,PLIST -Wnone,plist-sort -r -F
This project uses CMake to configure the software. Force the GNU
info files to be installed into ${CMAKE_INSTALL_INFODIR}, which is
defined by the GNUInstallDirs CMake module included by the
top-level CMakeLists.txt file. The corrct environment variables
are passed so that ${CMAKE_INSTALL_INFODIR} points into
${PKGINFODIR}.
Remove the subst.mk section that tried to force GNU info files to
be always installed under "info".
libgcrypt doesn't get used if openssl is installed. There's no way of disabling
openssl if it's found. Fix infodir using SUBST. Depends on latest version of
ucommon. From ChangeLog:
Changes from 2.1.1 to 2.1.2
- use ucommon cmake macros
- copyright assignment to Cherokees of Idaho
- copyright updates and corrections to bring current
Changes from 2.1.0 to 2.1.1
- fix endianness checks
- cleanup alloc/dealloc
- configure: fix libtoolize warning
- requires ucommon 6.2.2 for endian fixes
Changes from 2.0.9 to 2.1.0
- configure: add option to disable compilation of demos
- OSX: Check for macports glibtoolize.
- modernized cmake
- use standard header for malloc
- uptick of abi version for ucommon
2014-04-14 David Sugar (for 2.0.9)
Merged fix from Alexandre Lision for initial rtcp seq #
by pancake ;) <poppnk@users.sourceforge.net>.
Welcome to GNU ccRTP, the RTP protocol stack of GNU Common C++ and the
GNU project. GNU ccRTP was created as a "generic" and high performance
RTP stack and uses queued packet lists for both sending and receiving of
realtime data. A single scheduler thread both schedules delivery of
timestamped outgoing packets, and processes incoming packets into the
receive queue. A seperate thread or process can then feed data into the
stack for delivery and process pending requests without interfering with
the stack service thread itself.
