Overview

A collection of .spec files to make RPMs of software packages commonly used by the Network and Communications Systems Branch and others interested in network protocol research.

Built RPMs (and by extension, the packages that can be created with make rpm) are in rpmbuild/RPMS and rpmbuild/SRPMS. Note that make rpm assumes that it will be invoked upon a suitable OS (i.e., Red Hat, CentOS, Fedora, etc.).

Using the Repository

This requires GNU Make, which usually isn't a problem under Linux.

RPM package building has been tested under:

• CentOS 6, i686
• CentOS 6, x86_64
• CentOS 7, x86_64

Generally, RPMs can be made with

make -f Makefile.linux rpm

in the appropriate directory. If you get an error trying to mkdir /BUILD, this is a bug; please open an issue, but the workaround is to create a directory named rpmbuild at the same level as unpacked.

Source, both packed and unpacked, and pre-generated packages, including RPMs and SRPMs, are included in this repository for convenience. Only .spec and .patch files are strictly required for RPMs, or the unpacked source tree with the modified Makefiles, to make RPMs from scratch.

Versions are current as of their check-in time, but are unlikely to be kept up-to-date. Upstream has expressed interest in including the changes made to the Makefiles, so this may not be a problem moving forward.

TODO

• Package more software
  • SDT
    • Needs Java and a lot of work
  • SMF
    • Has an out-of-date Protolib, which no longer builds under Linux distributions without linux/netfilter_ipv4/ip_queue.h
    • Build a nightly build package instead
  • gpsLogger
    • Low priority package
• More packages
  • Debian package creation
    • Ubuntu 18.04 LTS
    • Ubuntu 16.04 LTS
    • Ubuntu 18.10 (i.e., current)
    • MGEN has the start of Debian packaging, based upon Debian's (old) 5.02 package, but it's not complete
  • -devel packages
    • Python bindings
      • Protolib is not building a shared library properly
      • Protolib's Python bindings don't build either, as a result; this is lower priority, though
    • Java bindings
      • Lower priority
    • C/C++ bindings
      • Protolib?
      • NORM will definitely have a -devel package as well as a regular package
  • Docs packages
    • Lower priority
    • Can be included in main RPM, under %files section, e.g.:

      %files
      %{_bindir}/foo
      %doc %{_docdir}/README

    • If there are a lot of docs, making a standalone package is preferred