How to Install and Uninstall watchman Package on openSUSE Leap
Last updated: November 26,2024
1. Install "watchman" package
Please follow the steps below to install watchman on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
watchman
Copied
2. Uninstall "watchman" package
In this section, we are going to explain the necessary steps to uninstall watchman on openSUSE Leap:
$
sudo zypper remove
watchman
Copied
3. Information about the watchman package on openSUSE Leap
Information for package watchman:
---------------------------------
Repository : Main Repository
Name : watchman
Version : 4.9.0-bp155.3.13
Arch : x86_64
Vendor : openSUSE
Installed Size : 939.1 KiB
Installed : No
Status : not installed
Source package : watchman-4.9.0-bp155.3.13.src
Upstream URL : https://facebook.github.io/watchman/
Summary : A file watching service
Description :
Watchman exists to watch files and record when they change. It can also trigger
actions (such as rebuilding assets) when matching files change.
* Watchman can recursively watch one or more directory trees (we call them
roots).
* Watchman does not follow symlinks. It knows they exist, but they show up the
same as any other file in its reporting.
* Watchman waits for a root to settle down before it will start to trigger
notifications or command execution.
* Watchman is conservative, preferring to err on the side of caution; it
considers files to be freshly changed when you start to watch them or when it
is unsure.
* You can query a root for file changes since you last checked, or the current
state of the tree
* You can subscribe to file changes that occur in a root
---------------------------------
Repository : Main Repository
Name : watchman
Version : 4.9.0-bp155.3.13
Arch : x86_64
Vendor : openSUSE
Installed Size : 939.1 KiB
Installed : No
Status : not installed
Source package : watchman-4.9.0-bp155.3.13.src
Upstream URL : https://facebook.github.io/watchman/
Summary : A file watching service
Description :
Watchman exists to watch files and record when they change. It can also trigger
actions (such as rebuilding assets) when matching files change.
* Watchman can recursively watch one or more directory trees (we call them
roots).
* Watchman does not follow symlinks. It knows they exist, but they show up the
same as any other file in its reporting.
* Watchman waits for a root to settle down before it will start to trigger
notifications or command execution.
* Watchman is conservative, preferring to err on the side of caution; it
considers files to be freshly changed when you start to watch them or when it
is unsure.
* You can query a root for file changes since you last checked, or the current
state of the tree
* You can subscribe to file changes that occur in a root