How to Install and Uninstall cvsps Package on openSuSE Tumbleweed
Last updated: November 07,2024
1. Install "cvsps" package
Learn how to install cvsps on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
cvsps
Copied
2. Uninstall "cvsps" package
Learn how to uninstall cvsps on openSuSE Tumbleweed:
$
sudo zypper remove
cvsps
Copied
3. Information about the cvsps package on openSuSE Tumbleweed
Information for package cvsps:
------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : cvsps
Version : 2.1-184.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 135.8 KiB
Installed : No
Status : not installed
Source package : cvsps-2.1-184.1.src
Upstream URL : http://www.cobite.com/cvsps/
Summary : A Program for Generating Patch Set Information from a CVS Repository
Description :
CVSps is a program for generating 'patchset' information from a CVS
repository. In this case, a patchset is defined as a set of changes
made to a collection of files, all committed at the same time (using a
single 'cvs commit' command). This information is valuable for seeing
the big picture of the evolution of a CVS project. While CVS tracks
revision information, it is often difficult to see what changes were
'atomically' committed to the repository.
------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : cvsps
Version : 2.1-184.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 135.8 KiB
Installed : No
Status : not installed
Source package : cvsps-2.1-184.1.src
Upstream URL : http://www.cobite.com/cvsps/
Summary : A Program for Generating Patch Set Information from a CVS Repository
Description :
CVSps is a program for generating 'patchset' information from a CVS
repository. In this case, a patchset is defined as a set of changes
made to a collection of files, all committed at the same time (using a
single 'cvs commit' command). This information is valuable for seeing
the big picture of the evolution of a CVS project. While CVS tracks
revision information, it is often difficult to see what changes were
'atomically' committed to the repository.