All Projects

This package contains vague terminology “Open Source”:

community/irrlicht-docs 1.8.4-1
    An open source high performance realtime 3D graphics engine.

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 high performance realtime 3D graphics engine.

This package contains vague terminology “Open Source”:

community/inn 2.6.1-1
    Complete open source Usenet system. De facto standard for handling news routing, news spool and serving the spool to customers.

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.

Complete free software Usenet system. De facto standard for handling news routing, news spool and serving the spool to customers.

We already have i3lock, this version is an enhanced version available in Arch AUR:
https://aur.archlinux.org/packages/i3lock-color https://aur.archlinux.org/packages/i3lock-color-git/

Create hypertools to replace libretools package for HyperbolaBSD and GNU/Linux

It’s long period to develop this package.
For now, a systemd-nspawn wrapper is being developed for “libretools”[0]

[0]:https://issues.hyperbola.info/index.php?do=details&task_id=86

This package contains vague terminology “Open Source”:

community/hyperion 1.03.2-9
    An opensource 'AmbiLight' implementation

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 'AmbiLight' implementation

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”:

community/gocr 0.50-2
    Open-source character recognition (OCR)

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 character recognition (OCR)

This package contains vague terminology “Open Source”:

community/goaccess 1.2-1
    An open source real-time web log analyzer and interactive viewer

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 real-time web log analyzer and interactive viewer

This package contains vague terminology “MP3 Player”:

community/gmtp 1.3.10-2
    A simple MP3 player client for MTP based devices

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

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

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

eg.

A simple audio player client for MTP based devices

This package contains vague terminology “Vendor”:

community/glide 0.12.3-1
    Dependency management and vendoring for Go projects

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

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

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

eg.

Dependency management and suppliering for Go projects

This package contains vague terminology “Open Source”:

community/glfw-x11 3.2.1-1
    A free, open source, portable framework for graphical application development (x11)

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, portable framework for graphical application development (x11)

This package contains vague terminology “Open Source”:

community/glfw-wayland 3.2.1-1
    A free, open source, portable framework for graphical application development (wayland)

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, portable framework for graphical application development (wayland)

This package contains vague terminology “Open Source”:

community/gerbv 2.6.1-4
    An open source Gerber file (RS-274X only) viewer

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 Gerber file (RS-274X only) viewer

As even the support for GCC 7 is now ending with the release of version 7.5 (https://gcc.gnu.org/ml/gcc/2019-11/msg00099.html) I’d like to propose a renewal of the building-stack - which I think is also needed in time. Also a renewal of the glibc would be good at all!

This package contains vague terminology “Open Source”:

community/freevo 1.9.0-14
    An open-source home theatre PC platform

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 home theatre PC platform

This package contains vague terminology “Open Source”:

community/freehdl 0.0.8-8
    An open-source (C++ generating) VHDL simulator

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 (C++ generating) VHDL simulator

This package contains vague terminology “Open Source”:

community/flightgear 2017.1.3-1
    An open-source, multi-platform flight simulator

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, multi-platform flight simulator

This package contains vague terminology “Open Source”:

community/flightgear-data 2017.1.3-1
    Base-Data for the opensource flight-simulator.

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.

Base-Data for the free-software flight-simulator.

This package contains vague terminology “Open Source” and “Linux”:

community/fcitx-mozc 2.20.2673.102-2
    Fcitx Module of A Japanese Input Method for Chromium OS, Windows, Mac and Linux (the Open Source Edition of Google Japanese Input)

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

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

It would be good example to set to have proper description of packages without using “Open Source” and “Linux” as operating system. Also it should avoid contains nonfree OSs in its description.

eg.

Fcitx Module of A Japanese Input Method for GNU/Linux (the Free Software Edition of Google Japanese Input)

Description:

community/ext3grep 0.10.2-4
    A tool to investigate an ext3 file system for deleted content and possibly recover it

Description is vague because of the word “content”. Why not say instead “data”?

See:
https://www.gnu.org/philosophy/words-to-avoid.html#Content

This package contains vague terminology “Open Source”:

community/dspam 3.10.2-14
    A scalable, open-source statistical anti-spam filter

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 scalable, free-software statistical anti-spam filter

This package contains vague terminology “Open Source”:

community/dsdp 5.8-1
    A free open source implementation of an interior-point method for semidefinite programming

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 an interior-point method for semidefinite programming

This package contains vague terminology “Content”:

community/drupal 8.3.2-1
    A PHP-based content management platform

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

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

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

eg.

A PHP-based web site revision system platform

This package contains vague terminology “Open Source”:

community/dokuwiki 20170219_b-1
    Simple to use and highly versatile Open Source wiki software

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.

Simple to use and highly versatile free wiki software

This package contains vague terminology “Open Source”:

community/displaycal 3.2.4.0-1
    Open Source Display Calibration and Characterization powered by Argyll CMS (Formerly known as dispcalGUI)

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 Display Calibration and Characterization powered by Argyll CMS (Formerly known as dispcalGUI)

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 “Linux”:

community/clamtk 5.24-1
    Easy to use, light-weight, on-demand virus scanner for Linux systems

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

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

It would be good example to set to have proper description of packages without using “Linux” as operating system.

eg.

Easy to use, light-weight, on-demand virus scanner for GNU/Linux systems

This package contains vague terminology “Open Source”:

community/cimg 1.7.1-1
    Open-source C++ toolkit for image processing

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 C++ toolkit for image processing

This package contains vague terminology “Open Source”:

community/bzrtp 1.0.5-1
    Opensource implementation of ZRTP keys exchange protocol

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 ZRTP keys exchange protocol

Description:

• replace deprecated GNU Bazaar to Brezy for Canis Major

Additional info:

• bzr 2.7.0-2
• GNU Bazaar will be unmaintained (for now, there are only bug fixes)
• GNU Bazaar only supports Python 2.
• Python 2.7 is the end of the Python 2 line of development. [0]
• There never will be an official Python 2.8 release.
• Or use Tauthon (fork of Python 2.7) as dependency.

Note: It needs a provide: bazaar and brezy

Steps to reproduce:

• broken package

This package contains vague terminology “Open Source”:

community/beignet 1.3.1-2
    An open source OpenCL implementation for Intel IvyBridge+ iGPUs

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 OpenCL implementation for Intel IvyBridge+ iGPUs

community/autoconf-archive 1:2017.03.21-1
    A collection of freely re-usable Autoconf macros

See:
https://www.gnu.org/philosophy/words-to-avoid.html#FreelyAvailable

Don’t use “freely available software” as a synonym for “free software.” The terms are not equivalent. Software is “freely available” if anyone can easily get a copy. “Free software” is defined in terms of the freedom of users that have a copy of it. These are answers to different questions.

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

aqemu only lists GNU/Linux and GNU/Hurd. Since LibertyBSD is also free it should also be added.

“appmenu-qt4”[0][2] is a deprecated package (release in 2012)[1] and use qt4 unsupported/non-lts software[3], but “appmenu-qt5” not contains any release source code[2]

$ pacman -Si appmenu-qt4
Repository : community
Name : appmenu-qt4
Version : 0.2.6-1
Description : Export Qt4 applications menus over D-Bus
Architecture : x86_64
URL : https://launchpad.net/appmenu-qt Licenses : GPL Groups : None
Provides : None
Depends On : libdbusmenu-qt4
Optional Deps : None
Conflicts With : appmenu-qt
Replaces : appmenu-qt
Download Size : 16.55 KiB
Installed Size : 48.00 KiB
Packager : Antonio Rojas arojas@archlinux.org Build Date : Tue 28 Feb 2017 05:59:31 AM -03
Validated By : MD5 Sum SHA-256 Sum Signature

[0]:https://launchpad.net/appmenu-qt (qt4)
[1]:https://launchpad.net/appmenu-qt/+download [2]:https://launchpad.net/appmenu-qt5 [3]:https://en.wikipedia.org/wiki/Qt_5.6_LTS

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

Add “3proxy”[0] package

Useful for tor on ftp proxy[1]

[0]:https://github.com/z3APA3A/3proxy [1]:https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/FTP

The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .

Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.

For the future of free computing, we need support architectures that do not come with such malware pre-installed, and RISC-V promises to be a great architecture example for low-power computers, laptops and embedded systems, also as ARM architecture replacement.

Devices like this are the future of computing that Respects Your Freedom and for that reason it’s a high priority for Hyperbola port all packages for the RISC-V architecture (riscv64) with multilib support.

NOTE: RISC-V porting is focused only for Hyperbola GNU/Linux-libre .

The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .

Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.

For the future of free computing, we need support architectures that do not come with such malware pre-installed, and the Power9-based Talos II promises to be a great architecture example for workstations and servers environments where Hyperbola is focused since is a fully free long-term support distribution.

Devices like this are the future of computing that Respects Your Freedom and for that reason it’s a high priority for Hyperbola port all packages for the POWER architecture (power64le).

NOTE: POWER porting is focused only for Hyperbola GNU/Linux-libre .

The unfortunate reality is that x86 computers come encumbered with built-in low-level backdoors like the Intel Management Engine , as well as nonfree boot firmware. This means that users can’t gain full control over their computers, even if they install a free operating system such as Hyperbola GNU/Linux-libre .

Hyperbola is working hard to fix these issues and getting closer every day, but for the time being, this is why many current Respects Your Freedom (RYF) offerings are refurbished older devices.

For the future of free computing, we need support architectures that do not come with such malware pre-installed, and ARM A7/A53 promises to be a great architecture example for low-power computers, laptops and embedded systems.

NOTE: ARM porting is focused only for HyperbolaBSD .