gnustep-back0.31-xlib
GNUstep GUI Backend (xlib)
It is a backend component for the GNUstep GUI Library.
The implementation of the GNUstep GUI Library is designed in two parts.
The first part is the front-end component which is independent of platform
and display system. This front-end is combined with a back-end
component which handles all of the display system dependent such as
specific calls to the X Window System.
python3-graph-tool
Efficient network analysis -- Python
graph-tool is an efficient Python module for manipulation and statistical
analysis of graphs (a.k.a. networks). Contrary to most other Python modules
with similar functionality, the core data structures and algorithms are
implemented in C++, making extensive use of template metaprogramming,
based heavily on the Boost Graph Library. This confers it a level of
performance that is comparable (both in memory usage and computation time)
to that of a pure C/C++ library.
libcap2
POSIX 1003.1e capabilities (library)
Libcap implements the user-space interfaces to the POSIX 1003.1e capabilities
available in Linux kernels. These capabilities are a partitioning of the all
powerful root privilege into a set of distinct privileges.
python3-gpiozero
simple interface to everyday GPIO components used with Raspberry Pi (Python 3)
gpiozero is an object-oriented wrapper around using various elelctronic
components with the GPIO interface on the Raspberry Pi. It allows
interacting with components like LEDs and buttons by defining them as
object instances which provide callback hooks to react to changes, e.g.
a button being pressed.
jtreg6
Regression Test Harness for the OpenJDK platform
jtreg is the test harness used by the OpenJDK test framework.
This framework is intended primarily for regression tests.
It can also be used for unit tests, functional tests, and even simple product
tests -- in other words, just about any type of test except a conformance test,
which belong in a TCK.
postgresql-14-hypopg
PostgreSQL extension adding support for hypothetical indexes.
An hypothetical, or virtual, index is an index that doesn't really exists, and
thus doesn't cost CPU, disk or any resource to create. They're useful to know
if specific indexes can increase performance for problematic queries, since
you can know if PostgreSQL will use these indexes or not without having to
spend resources to create them.