How to Install and Uninstall rubygem-rake-compiler.noarch Package on Fedora 35
Last updated: February 12,2025
1. Install "rubygem-rake-compiler.noarch" package
Here is a brief guide to show you how to install rubygem-rake-compiler.noarch on Fedora 35
$
sudo dnf update
Copied
$
sudo dnf install
rubygem-rake-compiler.noarch
Copied
2. Uninstall "rubygem-rake-compiler.noarch" package
Please follow the guidance below to uninstall rubygem-rake-compiler.noarch on Fedora 35:
$
sudo dnf remove
rubygem-rake-compiler.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the rubygem-rake-compiler.noarch package on Fedora 35
Last metadata expiration check: 5:44:36 ago on Wed Sep 7 02:25:42 2022.
Available Packages
Name : rubygem-rake-compiler
Version : 1.2.0
Release : 1.fc35
Architecture : noarch
Size : 31 k
Source : rubygem-rake-compiler-1.2.0-1.fc35.src.rpm
Repository : updates
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.2.0
Release : 1.fc35
Architecture : noarch
Size : 31 k
Source : rubygem-rake-compiler-1.2.0-1.fc35.src.rpm
Repository : updates
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.