How to Install and Uninstall ctpl.x86_64 Package on Fedora 39
Last updated: January 09,2025
1. Install "ctpl.x86_64" package
This guide covers the steps necessary to install ctpl.x86_64 on Fedora 39
$
sudo dnf update
Copied
$
sudo dnf install
ctpl.x86_64
Copied
2. Uninstall "ctpl.x86_64" package
Please follow the steps below to uninstall ctpl.x86_64 on Fedora 39:
$
sudo dnf remove
ctpl.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the ctpl.x86_64 package on Fedora 39
Last metadata expiration check: 3:59:33 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : ctpl
Version : 0.3.4
Release : 18.fc39
Architecture : x86_64
Size : 16 k
Source : ctpl-0.3.4-18.fc39.src.rpm
Repository : fedora
Summary : Template library and engine written in C
URL : http://ctpl.tuxfamily.org/
License : GPLv3+
Description : CTPL is a template library written in C. It allows fast and easy parsing of
: templates from many sources (including in-memory data and local and remote
: streaming, thanks to GIO) and fine control over template parsing environment.
:
: CTPL has following features:
: * It is a library, then it can be easily used from programs
: * Separated lexer and parser
: * It is written in portable C
: * Simple syntax
: * Fast and strict parsing
: * Possible in-memory parsing, allowing non-file data parsing and avoiding
: I/O-latency, through GIO's GMemoryInputStream and GMemoryOutputStream
Available Packages
Name : ctpl
Version : 0.3.4
Release : 18.fc39
Architecture : x86_64
Size : 16 k
Source : ctpl-0.3.4-18.fc39.src.rpm
Repository : fedora
Summary : Template library and engine written in C
URL : http://ctpl.tuxfamily.org/
License : GPLv3+
Description : CTPL is a template library written in C. It allows fast and easy parsing of
: templates from many sources (including in-memory data and local and remote
: streaming, thanks to GIO) and fine control over template parsing environment.
:
: CTPL has following features:
: * It is a library, then it can be easily used from programs
: * Separated lexer and parser
: * It is written in portable C
: * Simple syntax
: * Fast and strict parsing
: * Possible in-memory parsing, allowing non-file data parsing and avoiding
: I/O-latency, through GIO's GMemoryInputStream and GMemoryOutputStream