All Projects

$ pacman -Si iperf3
Repository      : community
Name            : iperf3
Version         : 3.1.7-1
Description     : Internet Protocol bandwidth measuring tool
Architecture    : x86_64
URL             : https://github.com/esnet/iperf
Licenses        : BSD
Groups          : None
Provides        : None
Depends On      : glibc
Optional Deps   : None
Conflicts With  : None
Replaces        : None
Download Size   : 62.46 KiB
Installed Size  : 181.00 KiB
Packager        : Timothy Redaelli <timothy.redaelli@gmail.com>
Build Date      : Fri 10 Mar 2017 01:06:09 PM -03
Validated By    : MD5 Sum  SHA-256 Sum  Signature

$ pacman -Ql iperf3
iperf3 /usr/
iperf3 /usr/bin/
iperf3 /usr/bin/iperf3
iperf3 /usr/include/
iperf3 /usr/include/iperf_api.h
iperf3 /usr/lib/
iperf3 /usr/lib/libiperf.so
iperf3 /usr/lib/libiperf.so.0
iperf3 /usr/lib/libiperf.so.0.0.0
iperf3 /usr/share/
iperf3 /usr/share/licenses/
iperf3 /usr/share/licenses/iperf3/
iperf3 /usr/share/licenses/iperf3/LICENSE
iperf3 /usr/share/man/
iperf3 /usr/share/man/man1/
iperf3 /usr/share/man/man1/iperf3.1.gz
iperf3 /usr/share/man/man3/
iperf3 /usr/share/man/man3/libiperf.3.gz

Warsow contains a library called steamlib which is built from the source. It’s useful only for Steam support which is nonfree software.

Description:

• Arch distributes a version of man-pages with manual pages from the POSIX standard. The man-pages project is permitted to distribute them and Andries Brouwer assumes that re-distribution by vendors is permitted as well. However, modification is definitively not allowed, hence this contribution by The Institute of Electrical and Electronics Engineers and The Open Group render the entire man-pages package nonfree. The way to solve it is remove all nonfree POSIX manual pages from man-pages package.

Additional info:
* package version(s)

• 4.11-1

* config and/or log files etc.

• License file (POSIX-COPYRIGHT):

The Institute of Electrical and Electronics Engineers (IEEE) and
The Open Group, have given us permission to reprint portions of
their documentation.

In the following statement, the phrase ``this text'' refers to
portions of the system documentation.

Portions of this text are reprinted and reproduced in electronic form
from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology
-- Portable Operating System Interface (POSIX), The Open Group Base
Specifications Issue 7, Copyright (C) 2013 by the Institute of Electri-
cal and Electronics Engineers, Inc and The Open Group.  (This is
POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
event of any discrepancy between this version and the original IEEE and
The Open Group Standard, the original IEEE and The Open Group Standard
is the referee document.  The original Standard can be obtained online
at http://www.unix.org/online.html .

This notice shall appear on any product containing this material.

Redistribution of this material is permitted so long as this notice and
the corresponding notices within each POSIX manual page are retained on
any distribution, and the nroff source is included. Modifications to
the text are permitted so long as any conflicts with the standard
are clearly marked as such in the text.

Steps to reproduce:

• See license in /usr/share/licenses/man-pages/POSIX-COPYRIGHT

This package contains vague terminology “Open Source”:

core/openssl 1.1.0.e-1
    The Open Source toolkit for Secure Sockets Layer and Transport Layer Security

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

The Free Software toolkit for Secure Sockets Layer and Transport Layer Security

This package contains vague terminology “Open Source”:

extra/aiksaurus 1.2.1-5
    A cross-platform, open-source thesaurus

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A cross-platform, free-software thesaurus

This package contains vague terminology “Open Source”:

extra/assimp 3.3.1-1
    Portable Open Source library to import various well-known 3D model formats in an uniform manner

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Portable Free Software library to import various well-known 3D model formats in an uniform manner

This package contains vague terminology “Open Source”:

extra/cmake 3.8.0-1
    A cross-platform open-source make system

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A cross-platform free-software make system

This package contains vague terminology “Open Source”:

extra/gstreamer 1.12.0-1
    GStreamer open-source multimedia framework core library

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

GStreamer free-software multimedia framework core library

This package contains vague terminology “Open Source”:

extra/java-openjfx 8.u121-1
    Java OpenJFX 8 client application platform (open-source implementation of JavaFX)

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Java OpenJFX 8 client application platform (free-software implementation of JavaFX)

This package contains vague terminology “Open Source”:

extra/java-openjfx-doc 8.u121-1
    Java OpenJFX 8 client application platform (open-source implementation of JavaFX) - documentation

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Java OpenJFX 8 client application platform (free-software implementation of JavaFX) - documentation

This package contains vague terminology “Open Source”:

extra/java-openjfx-src 8.u121-1
    Java OpenJFX 8 client application platform (open-source implementation of JavaFX) - sources

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Java OpenJFX 8 client application platform (free-software implementation of JavaFX) - sources

This package contains vague terminology “Open Source”:

extra/java-rhino 1.7.7.1-1.hyperbola1
    Open-source implementation of JavaScript written entirely in Java - JAR

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Free-software implementation of JavaScript written entirely in Java - JAR

This package contains vague terminology “Open Source”:

extra/kdegames-kigo 17.04.0-1 (kde-applications kdegames)
    An open-source implementation of the popular Go game

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free-software implementation of the popular Go game

This package contains vague terminology “Open Source”:

extra/libgdiplus 4.2-1
    An Open Source Implementation of the GDI+ API

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A Free Software Implementation of the GDI+ API

This package contains vague terminology “Open Source”:

extra/libical 2.0.0-2
    An open source reference implementation of the icalendar data type and serialization format

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free software reference implementation of the icalendar data type and serialization format

This package contains vague terminology “Open Source”:

extra/liblouis 3.0.0-2
    Open-source braille translator and back-translator

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Free-software braille translator and back-translator

This package contains vague terminology “Open Source”:

extra/libofa 0.9.3-6
    An open-source audio fingerprint by MusicIP

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free-software audio fingerprint by MusicIP

This package contains vague terminology “Open Source”:

extra/libomxil-bellagio 0.9.3-1
    An opensource implementation of the OpenMAX Integration Layer API

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free software implementation of the OpenMAX Integration Layer API

This package contains vague terminology “Open Source”:

extra/libupnp 1.6.21-1
    Portable Open Source UPnP Development Kit

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

Portable Free Software UPnP Development Kit

This package contains vague terminology “Open Source”:

extra/mlt 6.4.1-6
    An open source multimedia framework

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free software multimedia framework

This package contains vague terminology “Open Source”:

extra/mlt-python-bindings 6.4.1-6
    An open source multimedia framework

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free software multimedia framework

This package contains vague terminology “Open Source”:

extra/opencore-amr 0.1.5-1
    Open source implementation of the Adaptive Multi Rate (AMR) speech codec

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

extra/opencore-amr 0.1.5-1
    Free software implementation of the Adaptive Multi Rate (AMR) speech codec

no task description

no task description

This package contains vague terminology “Open Source”:

extra/openjpeg 1.5.2-1
    An open source JPEG 2000 codec

According to:
https://www.gnu.org/distros/free-system-distribution-guidelines.html

We shall avoid vague terminology such as “Open Source”, please see here:
https://www.gnu.org/philosophy/words-to-avoid.html#Open

It would be good example to set to have proper description of packages without using “Open Source”.

eg.

A free software JPEG 2000 codec