How to Install and Uninstall libgraphene-1_0-0 Package on openSuSE Tumbleweed
Last updated: November 08,2024
1. Install "libgraphene-1_0-0" package
Please follow the steps below to install libgraphene-1_0-0 on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
libgraphene-1_0-0
Copied
2. Uninstall "libgraphene-1_0-0" package
This guide covers the steps necessary to uninstall libgraphene-1_0-0 on openSuSE Tumbleweed:
$
sudo zypper remove
libgraphene-1_0-0
Copied
3. Information about the libgraphene-1_0-0 package on openSuSE Tumbleweed
Information for package libgraphene-1_0-0:
------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : libgraphene-1_0-0
Version : 1.10.8-1.9
Arch : x86_64
Vendor : openSUSE
Installed Size : 115.1 KiB
Installed : No
Status : not installed
Source package : graphene-1.10.8-1.9.src
Upstream URL : https://ebassi.github.io/graphene/
Summary : Thin type layer for graphic libraries
Description :
When creating graphic libraries you most likely end up dealing with points
and rectangles. If you're particularly unlucky, you may end up dealing
with affine matrices and 2D transformations. If you're writing a graphic
library with 3D transformations, though, you are going to hit the jackpot:
4x4 matrices, projections, transformations, vectors, and quaternions.
This library provides types and their relative API; it does not deal with
windowing system surfaces, drawing, scene graphs, or input. You're
supposed to do that yourself, in your own canvas implementation, which is
the whole point of writing the library in the first place.
------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : libgraphene-1_0-0
Version : 1.10.8-1.9
Arch : x86_64
Vendor : openSUSE
Installed Size : 115.1 KiB
Installed : No
Status : not installed
Source package : graphene-1.10.8-1.9.src
Upstream URL : https://ebassi.github.io/graphene/
Summary : Thin type layer for graphic libraries
Description :
When creating graphic libraries you most likely end up dealing with points
and rectangles. If you're particularly unlucky, you may end up dealing
with affine matrices and 2D transformations. If you're writing a graphic
library with 3D transformations, though, you are going to hit the jackpot:
4x4 matrices, projections, transformations, vectors, and quaternions.
This library provides types and their relative API; it does not deal with
windowing system surfaces, drawing, scene graphs, or input. You're
supposed to do that yourself, in your own canvas implementation, which is
the whole point of writing the library in the first place.