How to Install and Uninstall rubygem-liquid.noarch Package on Fedora 38
Last updated: November 28,2024
1. Install "rubygem-liquid.noarch" package
Please follow the guidance below to install rubygem-liquid.noarch on Fedora 38
$
sudo dnf update
Copied
$
sudo dnf install
rubygem-liquid.noarch
Copied
2. Uninstall "rubygem-liquid.noarch" package
Please follow the guidelines below to uninstall rubygem-liquid.noarch on Fedora 38:
$
sudo dnf remove
rubygem-liquid.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the rubygem-liquid.noarch package on Fedora 38
Last metadata expiration check: 0:37:46 ago on Sat Mar 16 22:59:57 2024.
Available Packages
Name : rubygem-liquid
Version : 4.0.3
Release : 13.fc38
Architecture : noarch
Size : 50 k
Source : rubygem-liquid-4.0.3-13.fc38.src.rpm
Repository : fedora
Summary : Secure, non-evaling end user template engine
URL : http://www.liquidmarkup.org
License : MIT
Description : Liquid is a template engine which was written with very specific requirements:
: * It has to have beautiful and simple markup. Template engines which don't
: produce good looking markup are no fun to use.
: * It needs to be non evaling and secure. Liquid templates are made so that
: users can edit them. You don't want to run code on your server which your
: users wrote.
: * It has to be stateless. Compile and render steps have to be separate so that
: the expensive parsing and compiling can be done once and later on you can
: just render it passing in a hash with local variables and objects.
Available Packages
Name : rubygem-liquid
Version : 4.0.3
Release : 13.fc38
Architecture : noarch
Size : 50 k
Source : rubygem-liquid-4.0.3-13.fc38.src.rpm
Repository : fedora
Summary : Secure, non-evaling end user template engine
URL : http://www.liquidmarkup.org
License : MIT
Description : Liquid is a template engine which was written with very specific requirements:
: * It has to have beautiful and simple markup. Template engines which don't
: produce good looking markup are no fun to use.
: * It needs to be non evaling and secure. Liquid templates are made so that
: users can edit them. You don't want to run code on your server which your
: users wrote.
: * It has to be stateless. Compile and render steps have to be separate so that
: the expensive parsing and compiling can be done once and later on you can
: just render it passing in a hash with local variables and objects.