How to Install and Uninstall melange Package on openSuSE Tumbleweed
Last updated: November 23,2024
1. Install "melange" package
Please follow the guidelines below to install melange on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
melange
Copied
2. Uninstall "melange" package
Please follow the step by step instructions below to uninstall melange on openSuSE Tumbleweed:
$
sudo zypper remove
melange
Copied
3. Information about the melange package on openSuSE Tumbleweed
Information for package melange:
--------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : melange
Version : 0.6.4-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 57.7 MiB
Installed : No
Status : not installed
Source package : melange-0.6.4-1.1.src
Upstream URL : https://github.com/chainguard-dev/melange
Summary : Build APKs from source code
Description :
Build apk packages using declarative pipelines.
Commonly used to provide custom packages for container images built with apko. The majority of apks are built for use with either the Wolfi or Alpine Linux ecosystems.
Key features:
* Pipeline-oriented builds. Every step of the build pipeline is defined and controlled by you, unlike traditional package managers which have distinct phases.
* Multi-architecture by default. QEMU is used to emulate various architectures, avoiding the need for cross-compilation steps.
--------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : melange
Version : 0.6.4-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 57.7 MiB
Installed : No
Status : not installed
Source package : melange-0.6.4-1.1.src
Upstream URL : https://github.com/chainguard-dev/melange
Summary : Build APKs from source code
Description :
Build apk packages using declarative pipelines.
Commonly used to provide custom packages for container images built with apko. The majority of apks are built for use with either the Wolfi or Alpine Linux ecosystems.
Key features:
* Pipeline-oriented builds. Every step of the build pipeline is defined and controlled by you, unlike traditional package managers which have distinct phases.
* Multi-architecture by default. QEMU is used to emulate various architectures, avoiding the need for cross-compilation steps.