This is a staging site. Uploads will not persist. Testing only.
libstd-rust-1.58
Rust standard libraries
Rust is a curly-brace, block-structured expression language. It
visually resembles the C language family, but differs significantly
in syntactic and semantic details. Its design is oriented toward
concerns of "programming in the large", that is, of creating and
maintaining boundaries - both abstract and operational - that
preserve large-system integrity, availability and concurrency.
libotbice-8.1-1
ORFEO Toolbox library - OTBIce
ORFEO Toolbox (OTB) is distributed as an open source library of image
processing algorithms. OTB is based on the medical image processing library
ITK and offers particular functionalities for remote sensing image processing
in general and for high spatial resolution images in particular.
libutil-h2o-perl
module to turn hashrefs into objects with accessors for keys
The Util::H2O module allows you to turn hashrefs into objects, so that
instead of $hash->{key} you can write $hash->key, plus you get protection
from typos. In addition, options are provided that allow you to whip up
really simple classes.
libotbimageio-8.1-1
ORFEO Toolbox library - OTBImageIO
ORFEO Toolbox (OTB) is distributed as an open source library of image
processing algorithms. OTB is based on the medical image processing library
ITK and offers particular functionalities for remote sensing image processing
in general and for high spatial resolution images in particular.
libotbiobsq-8.1-1
ORFEO Toolbox library - OTBIOBSQ
ORFEO Toolbox (OTB) is distributed as an open source library of image
processing algorithms. OTB is based on the medical image processing library
ITK and offers particular functionalities for remote sensing image processing
in general and for high spatial resolution images in particular.
python3-anyqt
PyQt/PySide compatibility layer for Qt4/Qt5/Qt6.
The package allows the programmer to program equally for two different
versions of Qt:
* At the top level AnyQt exports a Qt5 compatible module namespace along with
some minimal renames to better support portability between different
versions
* Which Qt API/backend is chosen can be controlled by a QT_API env variable
* The api can be chosen/forced programmatically (as long as no
PyQt4/PyQt5/PySide/PySide2 was already imported)
* Provides an optional compatibility import hook, that denys imports from
conflicting Qt api, or intercepts and fakes a Qt4 api imports, to use a Qt5
compatible API (some monkey patching is involved).