Home, sweet home!

This is where (questionably) useful packages are being held hostages.

A cross-distribution upstream release monitoring project.

This is where I keep spec files archived when there no need to build a package anymore.

This project was created for package elfutils via attribute OBS:Maintained

This project was created for package libblockdev via attribute OBS:Maintained

This project was created for package rpmdevtools via attribute OBS:Maintained

This project was created for package vim via attribute OBS:Maintained

This project was created for package kazam via attribute OBS:Maintained

This project was created for package libgedit-amtk via attribute OBS:Maintained

This project was created for package gnome-settings-daemon via attribute OBS:Maintained

This project was created for package memory-constraints via attribute OBS:Maintained

This project was created for package rpm via attribute OBS:Maintained

This project was created for package dkms via attribute OBS:Maintained

Containers

Build packages with debug symbols.

Longterm support kernels.

Let's see if we can improve the packaging and building of our Firefox.

* Try to use ld-limiter, so only link jobs get reduced - depending on the arch in use - rather the %jobs / %_smp_mflags. It would be really nice if FF migrated away from Autotools, though;
* Try to make use of OBSCPIO archive to help decrease disk space usage on OBS servers;
* Try to automate a pipeline that makes use of the Beta channel to improve the feeling for the next release version;

musl toolchain:

musl, GCC, binutils, GMP, MPFR, MPC, Linux, and ISL (optional).

Bootstrap process:

Build 1 --
Build musl-bootstrap with available binaries in OBS.
Build gcc-cross-musl against musl-bootstrap and libc++ with available binaries in OBS.
Build 1 is not full-featured and its binary is not ideal.

Build 2 --
Build musl, libc++, binutils, GMP, MPFR, MPC, Linux and optionally ISL with build 1.
Build GCC-musl against musl and libc++ with build 1.
Build 2 is full-featured and with ideal binary.

oscquery

Machine Learning and High Performance Computing Software Stack for AMD GPU
ROCm Binary Package Structure

ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools. In AMD’s package distributions, these software projects are provided as separate packages. This allows users to install only the packages they need, if they do not wish to install all of ROCm.

ROCm Core Components

* ROCk Kernel Driver: rock-dkms rock-dkms-firmware
* ROCr Runtime: hsa-rocr-devel
* ROCt Thunk Interface: hsakmt-roct, hsakmt-roct-devel

ROCm Support Software

* ROCm SMI: rocm-smi
* ROCm cmake: rocm-cmake
* rocminfo: rocminfo
* ROCm Bandwidth Test: rocm_bandwidth_test

ROCm Compilers

* Clang compiler: llvm-amdgpu
* HIP: hip_base, hip_doc, hip_rocclr, hip_samples
* ROCM Clang-OCL Kernel Compiler: rocm-clang-ocl

ROCm Device Libraries

* ROCm Device Libraries: rocm-device-libs
* ROCm OpenCL: rocm-opencl, rocm-opencl-devel

ROCm Development ToolChain

* Asynchronous Task and Memory Interface (ATMI): atmi
* ROCm Debug Agent: rocm_debug_agent
* ROCm Code Object Manager: comgr
* ROC Profiler: rocprofiler-devel
* ROC Tracer: roctracer-devel

ROCm Libraries

* rocALUTION: rocalution
* rocBLAS: rocblas
* hipBLAS: hipblas
* hipCUB: hipCUB
* rocFFT: rocfft
* rocRAND: rocrand
* rocSPARSE: rocsparse
* hipSPARSE: hipsparse
* ROCm SMI Lib: rocm-smi-lib64
* rocThrust: rocThrust
* MIOpen: MIOpen-HIP (for the HIP version), MIOpen-OpenCL (for the OpenCL version)
* MIOpenGEMM: miopengemm
* MIVisionX: mivisionx
* RCCL: rccl