How to Install and Uninstall luacheck Package on openSuSE Tumbleweed
Last updated: November 26,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "luacheck" package
This guide let you learn how to install luacheck on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
luacheck
Copied
2. Uninstall "luacheck" package
In this section, we are going to explain the necessary steps to uninstall luacheck on openSuSE Tumbleweed:
$
sudo zypper remove
luacheck
Copied
3. Information about the luacheck package on openSuSE Tumbleweed
Information for package luacheck:
---------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : luacheck
Version : 0.24.0-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 326,7 KiB
Installed : No
Status : not installed
Source package : luacheck-0.24.0-1.2.src
Summary : A a command-line tool for linting and static analysis of Lua code
Description :
Luacheck is a static analyzer and a linter for Lua. Luacheck detects
various issues such as usage of undefined global variables, unused variables
and values, accessing uninitialized variables, unreachable code and more.
Most aspects of checking are configurable: there are options for defining
custom project-related globals, for selecting set of standard globals
(version of Lua standard library), for filtering warnings by type and name of
related variable, etc.
The options can be used on the command line, put into a config or directly into
checked files as Lua comments.
---------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : luacheck
Version : 0.24.0-1.2
Arch : noarch
Vendor : openSUSE
Installed Size : 326,7 KiB
Installed : No
Status : not installed
Source package : luacheck-0.24.0-1.2.src
Summary : A a command-line tool for linting and static analysis of Lua code
Description :
Luacheck is a static analyzer and a linter for Lua. Luacheck detects
various issues such as usage of undefined global variables, unused variables
and values, accessing uninitialized variables, unreachable code and more.
Most aspects of checking are configurable: there are options for defining
custom project-related globals, for selecting set of standard globals
(version of Lua standard library), for filtering warnings by type and name of
related variable, etc.
The options can be used on the command line, put into a config or directly into
checked files as Lua comments.