How to Install and Uninstall vcs-diff-lint.noarch Package on Red Hat Enterprise Linux 8 (RHEL 8)
Last updated: November 26,2024
1. Install "vcs-diff-lint.noarch" package
This guide covers the steps necessary to install vcs-diff-lint.noarch on Red Hat Enterprise Linux 8 (RHEL 8)
$
sudo dnf update
Copied
$
sudo dnf install
vcs-diff-lint.noarch
Copied
2. Uninstall "vcs-diff-lint.noarch" package
This guide covers the steps necessary to uninstall vcs-diff-lint.noarch on Red Hat Enterprise Linux 8 (RHEL 8):
$
sudo dnf remove
vcs-diff-lint.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the vcs-diff-lint.noarch package on Red Hat Enterprise Linux 8 (RHEL 8)
Last metadata expiration check: 0:27:08 ago on Mon Feb 26 15:59:38 2024.
Available Packages
Name : vcs-diff-lint
Version : 4
Release : 2.el8
Architecture : noarch
Size : 21 k
Source : vcs-diff-lint-4-2.el8.src.rpm
Repository : epel
Summary : VCS Differential Code Analysis Tool
URL : https://github.com/fedora-copr/vcs-diff-lint
License : GPLv2+
Description : Analyze code, and print only reports related to a particular change.
:
: From within a VCS directory (only Git is supported for now) first analyze set of
: changed files against given changeset (origin/main by default) so we know what
: files need to be analyzed. Then run code analyzers (e.g. PyLint) against the
: old code (before changes), run analyzers against the actual code (not yet pushed
: changes), perform a diff (using csdiff utility), and finally print a set of
: added (or even fixed, as opt-in) analyzers' warnings.
Available Packages
Name : vcs-diff-lint
Version : 4
Release : 2.el8
Architecture : noarch
Size : 21 k
Source : vcs-diff-lint-4-2.el8.src.rpm
Repository : epel
Summary : VCS Differential Code Analysis Tool
URL : https://github.com/fedora-copr/vcs-diff-lint
License : GPLv2+
Description : Analyze code, and print only reports related to a particular change.
:
: From within a VCS directory (only Git is supported for now) first analyze set of
: changed files against given changeset (origin/main by default) so we know what
: files need to be analyzed. Then run code analyzers (e.g. PyLint) against the
: old code (before changes), run analyzers against the actual code (not yet pushed
: changes), perform a diff (using csdiff utility), and finally print a set of
: added (or even fixed, as opt-in) analyzers' warnings.