How to Install and Uninstall folly.x86_64 Package on Red Hat Enterprise Linux 9 (RHEL 9)

Last updated: November 25,2024

1. Install "folly.x86_64" package

This tutorial shows how to install folly.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                folly.x86_64
            
                    
    
    Copied

2. Uninstall "folly.x86_64" package

Please follow the step by step instructions below to uninstall folly.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                folly.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the folly.x86_64 package on Red Hat Enterprise Linux 9 (RHEL 9)

Last metadata expiration check: 0:08:25 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : folly
Version : 2023.04.24.00
Release : 4.el9
Architecture : x86_64
Size : 1.5 M
Source : folly-2023.04.24.00-4.el9.src.rpm
Repository : epel
Summary : An open-source C++ library developed and used at Facebook
URL : https://github.com/facebook/folly
License : ASL 2.0
Description : Folly (acronymed loosely after Facebook Open Source Library) is a library of
: C++14 components designed with practicality and efficiency in mind. Folly
: contains a variety of core library components used extensively at Facebook. In
: particular, it's often a dependency of Facebook's other open source C++ efforts
: and place where those projects can share code.
:
: It complements (as opposed to competing against) offerings such as Boost and of
: course std. In fact, we embark on defining our own component only when something
: we need is either not available, or does not meet the needed performance
: profile. We endeavor to remove things from folly if or when std or Boost
: obsoletes them.
:
: Performance concerns permeate much of Folly, sometimes leading to designs that
: are more idiosyncratic than they would otherwise be (see e.g. PackedSyncPtr.h,
: SmallLocks.h). Good performance at large scale is a unifying theme in all of
: Folly.