How to Install and Uninstall telepathy-mission-control Package on openSuSE Tumbleweed
Last updated: November 24,2024
1. Install "telepathy-mission-control" package
Please follow the step by step instructions below to install telepathy-mission-control on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
telepathy-mission-control
Copied
2. Uninstall "telepathy-mission-control" package
Please follow the instructions below to uninstall telepathy-mission-control on openSuSE Tumbleweed:
$
sudo zypper remove
telepathy-mission-control
Copied
3. Information about the telepathy-mission-control package on openSuSE Tumbleweed
Information for package telepathy-mission-control:
--------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : telepathy-mission-control
Version : 5.16.6-1.12
Arch : x86_64
Vendor : openSUSE
Installed Size : 999.7 KiB
Installed : No
Status : not installed
Source package : telepathy-mission-control-5.16.6-1.12.src
Upstream URL : http://mission-control.sourceforge.net/
Summary : Telepathy Mission Control instant messaging connection manager
Description :
Mission Control, or MC, is a Telepathy component providing a way for
"end-user" applications to abstract some of the details of connection
managers, to provide a simple way to manipulate a bunch of connection
managers at once, to remove the need to have in each program the
account definitions and credentials, to manage channel handling/request
and to manage presence statuses.
--------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : telepathy-mission-control
Version : 5.16.6-1.12
Arch : x86_64
Vendor : openSUSE
Installed Size : 999.7 KiB
Installed : No
Status : not installed
Source package : telepathy-mission-control-5.16.6-1.12.src
Upstream URL : http://mission-control.sourceforge.net/
Summary : Telepathy Mission Control instant messaging connection manager
Description :
Mission Control, or MC, is a Telepathy component providing a way for
"end-user" applications to abstract some of the details of connection
managers, to provide a simple way to manipulate a bunch of connection
managers at once, to remove the need to have in each program the
account definitions and credentials, to manage channel handling/request
and to manage presence statuses.