Packages

Hi André, you could make an init for the searx search engine, it happens that
I want to launch it from local to avoid being in searx.me or
searx.riseup.net.

I have seen that there is a PKGBUILD in AUR [0]. I think it is necessary to make one with the init Openrc

[0]: https://aur.archlinux.org/packages/searx-py3/

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/

Iosevka wins a poll about most beautiful fonts on reddit (/r/linux). This font is very similar than Droid Sans (Official Google Font) with many advantages:

1 - Has 5 types modes (lightest, light, normal, bold, super bold)
2 - Condensed and big sizes (perfect for visual impairments users)
3 - Very Legible on i3-wm, Sway, Conky bar
4 - OTF license (Freedom license)

Iosevka is already on AUR, but create a official package prevent bug or proprietary third parties apps (Yaourt, etc) be installed by beginners Hyperbola users.

Official Site:
https://github.com/be5invis/Iosevka

On AUR:
https://aur.archlinux.org/packages/ttf-iosevka

Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background.

Please implement plymouth as an optional package.

Hello,

Could it be possible to add this package :

multipath-tools

“Multipath tools for Linux (including kpartx)”

License : GPL2

to the repo ?

Thank you

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

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

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

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/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 “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” 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)

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

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/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/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

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

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.

This package contains vague terminology “Open Source”:

community/irrlicht 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.