How to Install and Uninstall texlive-gitinfo2 Package on openSUSE Leap
Last updated: November 12,2024
1. Install "texlive-gitinfo2" package
Learn how to install texlive-gitinfo2 on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
texlive-gitinfo2
Copied
2. Uninstall "texlive-gitinfo2" package
This guide let you learn how to uninstall texlive-gitinfo2 on openSUSE Leap:
$
sudo zypper remove
texlive-gitinfo2
Copied
3. Information about the texlive-gitinfo2 package on openSUSE Leap
Information for package texlive-gitinfo2:
-----------------------------------------
Repository : Main Repository
Name : texlive-gitinfo2
Version : 2021.189.2.0.7svn38913-150400.17.1
Arch : noarch
Vendor : SUSE LLC
Installed Size : 12.5 KiB
Installed : No
Status : not installed
Source package : texlive-specs-k-2021-150400.17.1.src
Upstream URL : http://www.tug.org/texlive/
Summary : Access metadata from the git distributed version control system
Description :
The package makes it possible to incorporate git version
control metadata into documents. For memoir users, the package
provides the means to tailor page headers and footers to use
the metadata. gitinfo2 is a new release of gitinfo. The changes
to version 2 are not backward-compatible, and the package name
has been changed to avoid impact on existing users'
repositories. All new repositories should use this version of
the package.
-----------------------------------------
Repository : Main Repository
Name : texlive-gitinfo2
Version : 2021.189.2.0.7svn38913-150400.17.1
Arch : noarch
Vendor : SUSE LLC
Installed Size : 12.5 KiB
Installed : No
Status : not installed
Source package : texlive-specs-k-2021-150400.17.1.src
Upstream URL : http://www.tug.org/texlive/
Summary : Access metadata from the git distributed version control system
Description :
The package makes it possible to incorporate git version
control metadata into documents. For memoir users, the package
provides the means to tailor page headers and footers to use
the metadata. gitinfo2 is a new release of gitinfo. The changes
to version 2 are not backward-compatible, and the package name
has been changed to avoid impact on existing users'
repositories. All new repositories should use this version of
the package.