Return to obtaining.rst CVS log

Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / iperf / docs

Annotation of embedaddon/iperf/docs/obtaining.rst, revision 1.1

1.1     ! misho       1: .. _obtaining:
        !             2: 
        !             3: Obtaining iperf3
        !             4: ================
        !             5: 
        !             6: Binary Distributions
        !             7: --------------------
        !             8: 
        !             9: Binary packages are available for several supported operating systems:
        !            10: 
        !            11: * FreeBSD:  `benchmarks/iperf3
        !            12:   <http://freshports.org/benchmarks/iperf3>`_ in the FreeBSD Ports Collection
        !            13: * Fedora / CentOS: `iperf3
        !            14:   <https://apps.fedoraproject.org/packages/iperf3/>`_ and
        !            15:   `iperf3-devel
        !            16:   <https://apps.fedoraproject.org/packages/iperf3-devel>`_ in Fedora
        !            17:   19 and 20 and in Fedora EPEL 5, 6, and 7.
        !            18: 
        !            19: Source Distributions
        !            20: --------------------
        !            21: 
        !            22: Source distributions of iperf are available as compressed (gzip)
        !            23: tarballs at:
        !            24: 
        !            25: http://downloads.es.net/pub/iperf/
        !            26: 
        !            27: **Note:**  Due to a software packaging error, the 3.0.2 release
        !            28: tarball was not compressed, even though its filename had a ``.tar.gz``
        !            29: suffix.
        !            30: 
        !            31: **Note:**  GitHub, which currently hosts the iperf3 project, supports
        !            32: a "Releases" feature, which can automatically generate ``.zip`` or ``.tar.gz``
        !            33: archives, on demand, from tags in the iperf3 source tree.  These tags are
        !            34: created during the release engineering process to mark the exact
        !            35: version of files making up a release.
        !            36: 
        !            37: In theory, the ``.tar.gz`` files produced by GitHub contain the same
        !            38: contents as what are in the official tarballs, note that the tarballs
        !            39: themselves will be different due to internal timestamps or other
        !            40: metadata.  Therefore these files will *not* match the published SHA256
        !            41: checksums and no guarantees can be made about the integrity of the
        !            42: files.  The authors of iperf3 always recommend downloading source
        !            43: distributions from the the directory above (or a mirror site), and
        !            44: verifying the SHA256 checksums before using them for any purpose, to
        !            45: ensure the files have not been tampered with.
        !            46: 
        !            47: Source Code Repository
        !            48: ----------------------
        !            49: 
        !            50: The iperf3 project is hosted on GitHub at:
        !            51: 
        !            52: https://github.com/esnet/iperf
        !            53: 
        !            54: The iperf3 source code repository can be checked out directly from
        !            55: GitHub using:
        !            56: 
        !            57: ``git clone https://github.com/esnet/iperf.git``
        !            58: 
        !            59: Primary development for iperf3 takes place on CentOS 6 Linux, FreeBSD 10,
        !            60: and MacOS X 10.8. At this time, these are the only officially supported
        !            61: platforms, however there have been some reports of success with
        !            62: OpenBSD, Android, and other Linux distributions.