-
libuuid-2.22.2-7.fc18.armv6hl
This is the universally unique ID library, part of util-linux.
The libuuid library generates and parses 128-bit universally unique
id's (UUID's). A UUID is an identifier that is unique across both
space and time, with respect to the space of all UUIDs. A UUID can
be used for multiple purposes, from tagging objects with an extremely
short lifetime, to reliably identifying very persistent objects
across a network.
See also the "uuid" package, which is a separate implementation.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libuuid-2.28-2.lbn19.x86_64
This is the universally unique ID library, part of util-linux.
The libuuid library generates and parses 128-bit universally unique
id's (UUID's). A UUID is an identifier that is unique across both
space and time, with respect to the space of all UUIDs. A UUID can
be used for multiple purposes, from tagging objects with an extremely
short lifetime, to reliably identifying very persistent objects
across a network.
See also the "uuid" package, which is a separate implementation.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libuv-1.9.1-1.lbn19.x86_64
libuv is a new platform layer for Node. Its purpose is to abstract IOCP on
Windows and libev on Unix systems. We intend to eventually contain all platform
differences in this library.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libv4l-0.9.5-2.fc19.armv6hl
libv4l is a collection of libraries which adds a thin abstraction layer on
top of video4linux2 devices. The purpose of this (thin) layer is to make it
easy for application writers to support a wide variety of devices without
having to write separate code for different devices in the same class. libv4l
consists of 3 different libraries: libv4lconvert, libv4l1 and libv4l2.
libv4lconvert offers functions to convert from any (known) pixel-format
to V4l2_PIX_FMT_BGR24 or V4l2_PIX_FMT_YUV420.
libv4l1 offers the (deprecated) v4l1 API on top of v4l2 devices, independent
of the drivers for those devices supporting v4l1 compatibility (which many
v4l2 drivers do not).
libv4l2 offers the v4l2 API on top of v4l2 devices, while adding for the
application transparent libv4lconvert conversion where necessary.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libv4l-1.6.2-1.lbn19.x86_64
libv4l is a collection of libraries which adds a thin abstraction layer on
top of video4linux2 devices. The purpose of this (thin) layer is to make it
easy for application writers to support a wide variety of devices without
having to write separate code for different devices in the same class. libv4l
consists of 3 different libraries: libv4lconvert, libv4l1 and libv4l2.
libv4lconvert offers functions to convert from any (known) pixel-format
to V4l2_PIX_FMT_BGR24 or V4l2_PIX_FMT_YUV420.
libv4l1 offers the (deprecated) v4l1 API on top of v4l2 devices, independent
of the drivers for those devices supporting v4l1 compatibility (which many
v4l2 drivers do not).
libv4l2 offers the v4l2 API on top of v4l2 devices, while adding for the
application transparent libv4lconvert conversion where necessary.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libva-1.1.1-2.fc19.armv6hl
Libva is a library providing the VA API video acceleration API.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libva-1.4.1-1.lbn19.x86_64
Libva is a library providing the VA API video acceleration API.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libvdpau-0.6-1.fc19.armv6hl
VDPAU is the Video Decode and Presentation API for UNIX.
It provides an interface to video decode acceleration and presentation
hardware present in modern GPUs.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libvdpau-0.7-1.fc19.x86_64
VDPAU is the Video Decode and Presentation API for UNIX. It provides an
interface to video decode acceleration and presentation hardware present in
modern GPUs.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
-
libverto-0.2.6-4.lbn19.x86_64
libverto provides a way for libraries to expose asynchronous interfaces
without having to choose a particular event loop, offloading this
decision to the end application which consumes the library.
If you are packaging an application, not library, based on libverto,
you should depend either on a specific implementation module or you
can depend on the virtual provides 'libverto-module-base'. This will
ensure that you have at least one module installed that provides io,
timeout and signal functionality. Currently glib is the only module
that does not provide these three because it lacks signal. However,
glib will support signal in the future.
Located in
LBN
/
…
/
Core Linux
/
BastionLinux 19
