How to Install and Uninstall rubygem-rake-compiler.noarch Package on Rocky Linux 9
Last updated: January 10,2025
1. Install "rubygem-rake-compiler.noarch" package
Here is a brief guide to show you how to install rubygem-rake-compiler.noarch on Rocky Linux 9
$
sudo dnf update
Copied
$
sudo dnf install
rubygem-rake-compiler.noarch
Copied
2. Uninstall "rubygem-rake-compiler.noarch" package
This tutorial shows how to uninstall rubygem-rake-compiler.noarch on Rocky Linux 9:
$
sudo dnf remove
rubygem-rake-compiler.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the rubygem-rake-compiler.noarch package on Rocky Linux 9
Last metadata expiration check: 1:10:53 ago on Fri Feb 16 06:49:52 2024.
Available Packages
Name : rubygem-rake-compiler
Version : 1.1.9
Release : 2.el9
Architecture : noarch
Size : 36 k
Source : rubygem-rake-compiler-1.1.9-2.el9.src.rpm
Repository : epel
Summary : Rake-based Ruby C Extension task generator
URL : http://rake-compiler.rubyforge.org/
License : MIT
Description : rake-compiler aims to help Gem developers while dealing with
: Ruby C extensions, simplifiying the code and reducing the duplication.
:
: It follows *convention over configuration* and set an standarized
: structure to build and package C extensions in your gems.
:
: This is the result of expriences dealing with several Gems
: that required native extensions across platforms and different
: user configurations where details like portability and
: clarity of code were lacking.
Available Packages
Name : rubygem-rake-compiler
Version : 1.1.9
Release : 2.el9
Architecture : noarch
Size : 36 k
Source : rubygem-rake-compiler-1.1.9-2.el9.src.rpm
Repository : epel
Summary : Rake-based Ruby C Extension task generator
URL : http://rake-compiler.rubyforge.org/
License : MIT
Description : rake-compiler aims to help Gem developers while dealing with
: Ruby C extensions, simplifiying the code and reducing the duplication.
:
: It follows *convention over configuration* and set an standarized
: structure to build and package C extensions in your gems.
:
: This is the result of expriences dealing with several Gems
: that required native extensions across platforms and different
: user configurations where details like portability and
: clarity of code were lacking.