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

Last updated: June 25,2024

1. Install "ustl.x86_64" package

Please follow the step by step instructions below to install ustl.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9)

$ sudo dnf update $ sudo dnf install ustl.x86_64

2. Uninstall "ustl.x86_64" package

Here is a brief guide to show you how to uninstall ustl.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9):

$ sudo dnf remove ustl.x86_64 $ sudo dnf autoremove

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

Last metadata expiration check: 1:26:12 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : ustl
Version : 2.8
Release : 9.el9
Architecture : x86_64
Size : 48 k
Source : ustl-2.8-9.el9.src.rpm
Repository : epel
Summary : A size-optimized STL implementation
URL : http://msharov.github.io/ustl/
License : MIT
Description : The C++ standard template library (STL) is a collection of common containers
: and algorithms in template form. Unfortunately its standard incarnation
: shipped with gcc is implemented without much concern for code size. Not only
: is the library itself large, the current version being over a megabyte in
: size, but with all the code you instantiate by using a vector for each of
: your containers, it is easy to become fearful and opt for using static
: arrays instead or, worse yet, abandon C++ altogether for C. This is
: especially painful to former DOS assembly programmers like myself, who fret
: endlessly when the size of the executable crosses the magic 64k boundary,
: forgetting that nobody cares about memory anymore.
:
: Of course, these days everyone has gigabytes of RAM and has no compunction
: about loading up OpenOffice, whose source tree is over a gigabyte in size.
: Why then bother with saving a kilobyte of code here and there? I can't really
: say. Maybe it's that warm fuzzy knowledge that you are making maximum possible
: use of your computer's resources. Maybe it's that thrill you get after
: expressing your program's functionality in the fewest possible instructions
: and the minimum imaginable overhead. Or maybe it really is of no importance
: and any code bloat will be easily overcome by faster processors in some near
: future. I just know what I like, and it's the sight of clean, concise, and
: fast code. Therefore this library.