Installing a DEB package in Ubuntu. Once again about deb packages How to open a file with a deb extension
$ sudo apt-get install dh_make
Preparing the source folder
In order to dh_make and other utilities could work with the source folder, you need to bring it into a specific form.The folder should be called package-name-version. Those. if I have a folder Plugins with the program version 0.1, then I create a folder called plugins-0.1.
$ ls VKSPlugins $ mv VKSPlugins/ libvksplugins-0.1 $ ls libvksplugins-0.1
Now you need to create an archive with this folder. The archive must contain in the name *.orig.tar.gz, i.e.:
$ tar -zcf libvksplugins_0.1.orig.tar.gz libvksplugins-0.1 $ ls libvksplugins-0.1 libvksplugins_0.1.orig.tar.gz
The last preparatory step is to create a folder in the source folder debian with many service files. To do this, you need to run the command:
$ cd libvksplugins-0.1/ $ dh_make Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch? l Maintainer name: User Name Email-Address: [email protected] Date: Wed, 19 Aug 2015 14:55:53 +0300 Package Name: libvkplugins Version: 0.1 License: blank Type of Package: Single Hit
While executing this command, you will be asked what type of archive we are creating; the simplest one is single.
About the package type
Actually the documentation says to select option only single. Because I couldn't understand all the requirements for a package like library but I’m quite happy with the result, then the description will continue to focus on a package like library.
Package setup
All package customization occurs by editing files in the directory debian. Let's look at the files that we will use:- changelog - package history.
- control - main package config;
- rules - an analogue of the Makefile for the package;
changelog
This file contains the package's modification history and the current version of the package. Let's look at its contents:$ cat changelog libvkplugins (0.1-1) unstable; urgency=low * Initial release (Closes: #nnnn)
At the beginning there is the name of the package - libvksplugins, then his version. The version is divided into two parts by the “-” symbol. The first part shows the version of the program in the package, the second the “revision” of the package. A revision is a package version, i.e. if there was no such package before, then the revision is equal to 1. If there was already a package with such a version of the program, but changes occurred in it, then the revision is increased.
Word unstable indicates that the package is not stable, i.e. it has not been tested properly on users' machines.
Inscription urgency=low shows the urgency of the change. Because there is no urgency, then the value is low. If we were making a package to fix a serious vulnerability or bug, then the value could be set to high.
After the first line there is an empty line, followed by the first entry:
* Initial release (Closes: #nnnn)
In Debian, changelog is used to automatically close bugs in software bug tracking systems. Because in this case, I do not use such a system, then this line takes the form:
*Initial release
Comment
When checking a package with a program lintian, absence Closes: #XXXX is considered an error.
The last line is the signature of the person who made the entry. It contains the name and address, as well as the date modified.
After installing the deb package, the file changelog installed in
/usr/share/doc/<пакет>/changelog.Debian.gz
control
File debian/control is the main config when creating a deb package. Here is an example of such a file:$ cat control Source: libvkplugins Priority: optional Maintainer: User Name
You can see that the file is divided into sections using empty lines. Each section describes one package created from the source folder. Let's look at them in order:
Source This section tells you to create a source code package. The parameter specified libvksplugins, this means that the source package will be called libvksplugins.
Priority This section sets the priority of the packet. Because the system can do just fine without a new package, then the section value is set to optional. Those. this package is not required for installation. Read more about priorities.
Maintainer This section describes the contact details of the person creating the package. Its format is quite simple and does not require additional description.
Build-Depends One of the most important sections that installs package dependencies. The dependencies listed in this section must be satisfied in order for the package to be built. Those. The list of dependencies for assembly and installation may differ.
It can be seen that they are dependent debhelper (>= 9), cmake. Addiction debhelper (>= 9) set by default for all packages. It is needed for the correct operation of programs like dh_*.
Second element cmake was added because the source folder contained the file CMakeLists.txt, i.e. the assembly system is used for assembly CMake. To find out what dependencies a program has, you can read its documentation. In addition, you can use the command dpkg-depcheck. This command should be run like this:
$ dpkg-depcheck -d ./configure
But, because When using CMake there is no configuration script, then I use it like this:
$ mkdir build && cd build $ dpkg-depcheck -d cmake ../ ..... Packages needed: libxml2:amd64 cmake libkrb5support0:amd64 language-pack-ru-base libnettle4:amd64 ..... libedit2:amd64 libtasn1 -6:amd64 qt4-qmake libgssapi-krb5-2:amd64 libhcrypto4-heimdal:amd64 ..... libroken18-heimdal:amd64 libsqlite3-0:amd64 libqt4-dev libssl1.0.0:amd64 .....
Notable ones here include:
Cmake
qt4-qmake
libqt4-dev
The rest are data dependencies. Moreover, cmake is already in the list of assembly dependencies. In principle, you can leave it as is or specify the version you are using:
$ apt-cache show cmake | grep Version: Version: 2.8.12.2-0ubuntu6
At the same time, CMakeLists.txt indicates the version of cmake that needs to be used:
$ cat CMakeLists.txt | grep cmake_minimum cmake_minimum_required(VERSION 2.8.4)
I think that the developer knows better, and therefore I indicate the version from CMakeLists.txt. For Qt 4, everything is clear with version numbers, but to clear our conscience, let’s check their versions as well:
$ apt-cache show qt4-qmake | grep Version: Version: 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1.1 Version: 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 $ apt-cache show libqt4-dev | grep Version: Version: 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1.1 Version: 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1
Those. for Qt 4 we specify version 4.8.6:
Build-Depends: debhelper (>= 9), cmake (>= 2.8.4), qt4-qmake (>= 4.8.6), libqt4-dev (>= 4.8.6)
Standards-Version The version of the standard under which the file was created. This value does not need to be changed.
Section. Section for the package, i.e. a group of packages that perform a single task. Debian Policy section 2.4 describes this issue in more detail.
Homepage Project home page. Because I wrote this code and it doesn’t have a page, I just delete this line.
Other packages After the section of the file that describes the source package, there are sections that describe other packages created from the source package. Package creation scheme:
From the diagram it is clear that from the source code of the program, I want to get 4 packages:
- source code package;
- package with the binary (the library itself);
- development package (header files);
- documentation package.
My personal answer to this question is that such division helps to structure the program in the way I want to work with it. For development I will install the dev package, but not for use.
In addition to the packages described above, you can create a dbg package with a debug build of the program. This can be useful if the program crashes and you have a debugger at hand. However, I still couldn't figure out how to do this. The documentation doesn't answer this question. If I do it as described in it, then I either get an empty package or get a bunch of errors during assembly.
The diagram in the figure above shows that the source package is called libvksplugins_source, however, the control file states that the source package will be called libvksplugins. In fact, it will actually be called libvksplugins, and the package with binaries will be called libvksplugins...deb. The essence of this confusion is that the source package is a tar archive and service files, while the binary package is an archive with the deb extension.
Setting up a library package Let's look carefully at the description of the library package:
Package: libvksplugins
Architecture: any
Depends: $(shlibs:Depends), $(misc:Depends)
Description: Library for creating plugins with VKS 2
This library provides a mechanism for creating plugins
to use in project VKS 2.
Parameter Architecture sets the architecture of the package being built. Meaning any means that after building the binaries, the required architecture will be substituted by the build system. Those. on a 64-bit machine, you get a package ..._amd64... and for a 32-bit package ..._i386....
For packages containing scripts or texts, you need to specify the value as all.
The third line describes the dependencies of the package being created. Here's how it's described in Chapter 4 of the Debian Beginner's Guide:
Utility dh_shlibdeps Calculates a binary package's dependencies on shared libraries. It generates a list of ELF executables and shared libraries that it finds for each binary package. This list is substituted instead $(shlibs:Depends).Utility dh_perl calculates Perl dependencies. It generates a list of perl or perlapi dependencies for each binary package. This list is substituted instead $(perl:Depends).
Some debhelper package commands may add dependencies to your generated package. Each command generates a list of required packages for each binary package. This list is substituted instead
$(misc:Depends).Utility dh_gencontrol generates a file DEBIAN/control for each binary package, replacing $(shlibs:Depends), $(perl:Depends), $(misc:Depends) etc. for the obtained values.
Those. This line indicates that the package builder will determine the dependencies itself.
The last section of this section is the package description. The first line contains a brief description, subsequent lines contain a more detailed description. A detailed description must have a specific format:
- the line must begin with a space;
- the line should not be longer than 80 characters;
- an empty line must begin with a space and consist of a period character.
Package: libvksplugins-dev
Section: libdevel
Architecture: any
Depends: libvksplugins (= $(binary:Version)), $(misc:Depends)
Description: Development package for libvkplugins
This package provides development files for
library libvkplugins.
.
Also, it contains pkg-config file, to use.
In this example, the interesting line is Depends. It states that this package will depend on the library package libvksplugins, and ( = $(binary:Version)) indicates that the versions of the binary package and the development package must strictly match. This is an important point because the header files must strictly match the binaries.
Setting up the documentation package Documentation is supplied with the library, so that it is in a separate package, we add its description:
Package: libvksplugins-doc
Architecture: all
Depends: $(shlibs:Depends), $(misc:Depends)
Description: Documentation for libvkplugins
Package contains html documentation files for libvksplugins
Everything should be clear here.
rules
This file is analogous to a Makefile for building packages. By default, it is created like this:$ cat rules #!/usr/bin/make -f # See debhelper(7) (uncomment to enable) # output every command that modifies files on the build system. #DH_VERBOSE = 1 # see EXAMPLES in dpkg-buildflags(1) and read /usr/share/dpkg/* DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/default.mk # see FEATURE AREAS in dpkg-buildflags(1) # export DEB_BUILD_MAINT_OPTIONS = hardening=+all # see ENVIRONMENT in dpkg-buildflags(1) # package maintainers to append CFLAGS #export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic # package maintainers to append LDFLAGS #export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed # main packaging script based on dh7 syntax %: dh $@ # debmake generated override targets # This is example for Cmake (See http://bugs.debian.org/641051) #override_dh_auto_configure: # dh_auto_configure -- \ # -DCMAKE_LIBRARY_PATH=$ (DEB_HOST_MULTIARCH)
It can be seen that this is a bash script with Makefile syntax. The only interesting design here is
%:dh$@
This is a template that, for all purposes, calls the dh command and passes arguments to it. To build the package, it is important that the text dh$@ I started reading from the tab character. Those. Indentation is not spaces, but tabs.
Because the sources use the CMake build system, you need to change this entry as follows:
%: dh $@ --buildsystem=cmake
Package Contents
After we have indicated in debian/control which packages we want to receive, we need to specify which files to put in which package. To do this, for each package name from the file control, you need to create it in the folder debian two files. The first one should be called package.dirs, and second package.install. The essence of the files is that the first specifies which folders need to be created for the package, and the second specifies which files to include in the package.Let's look at their contents:
$ cat libvksplugins-dev.dirs usr/lib usr/include $ cat libvksplugins-dev.install usr/include/* usr/lib/lib*.a usr/lib/lib*.so usr/lib/pkgconfig/* usr/ share/pkgconfig/*
An important point is the absence of an initial fraction in the paths and the absence of a fraction at the end of the path to the folder. After checking where CMake installs the library files, you can generate the following files:
$ for item in $(ls libvksplugins*); do echo "$item:"; cat $item; done libvksplugins-dev.dirs: usr/include/dep572 usr/lib/pkgconfig libvksplugins-dev.install: usr/include/dep572/plugins/* usr/lib/dep572/lib*.so usr/lib/pkgconfig/* libvksplugins .dirs: usr/lib/dep572 libvksplugins-doc.dirs: usr/share/doc/libplugins-0.1 libvksplugins-doc.install: usr/share/doc/libplugins-0.1/*.tgz libvksplugins.install: usr/lib/ dep572/lib*.so.*
Completing setup
Because the sources are mine, I don’t have any additional descriptions or copyright restrictions, so I delete all unnecessary files from the debian directory.Building packages
After configuration, building packages is quite simple; you need to run the command in the project folder (which includes the debian subfolder):$ dpkg-buildpackage -rfakeroot -us -uc
Options -us -uc they say that there is no need to sign created packages with a gpg key. They can be omitted if the default signing key gpg is configured. I also didn’t understand how to specify the default signing key. If everything went well, then we will have a set of packages lying around in the folder above:
$ ls -l ../ total 748 drwxrwxr-x 10 user user 4096 Aug 20 10:46 libvksplugins-0.1 -rw-rw-r-- 1 user user Aug 2210 20 10:47 libvksplugins_0.1-1_amd64.changes -rw-r--r-- 1 user user 6418 Aug. 20 10:47 libvksplugins_0.1-1_amd64.deb -rw-rw-r-- 1 user user Aug 1504 20 10:46 libvksplugins_0.1-1.debian.tar.xz -rw-rw-r-- 1 user user Aug 1008 20 10:46 libvksplugins_0.1-1.dsc -rw-rw-r-- 1 user user 36713 Aug. 19 14:52 libvksplugins_0.1.orig.tar.gz -rw-r--r-- 1 user user Aug 3262 20 10:47 libvksplugins-dev_0.1-1_amd64.deb -rw-r--r-- 1 user user 699564 Aug. 20 10:47 libvksplugins-doc_0.1-1_all.deb
Conclusion
If you have read this far, it means you love reading.This text is the result of my experience implementing deb packages at work. Experience has shown that the presence of a network repository (reprepro) and careful tracking of versions makes it possible to easily update and test various software versions on a fleet of 30 machines with Astra Linux 1.3, 1.4 and Elbrus OS systems.
deb- extension of file names of “binary” packages for distribution and installation of software on the OS of the Debian project, and others using the dpkg package management system. And today we'll look at three command line tools to help you install a local Debian package.
If you are asking yourself: “How can I install a Deb package on Ubuntu or Debian?”, then you have come to the right place.
You can right-click on the downloaded DEB package and select install from the context menu, but using a graphical installer it will be very slow compared to terminal commands. Here are 3 different command line tools to help you install Deb packages. They are also Dpkg, Gdebi and APT.
Dpkg
dpkg is the software that forms the basis of the package management system in Debian and a number of other Debian-based operating systems, such as Ubuntu. dpkg is used to install, remove, and obtain information about .deb packages.
Use dpkg to install a local Debian package as shown below.
Sudo dpkg -i package_version.deb
Dpkg by itself can't solve the dependency problem because it doesn't understand repositories. But you can use the following command to solve this problem.
Sudo apt install -f
Gdebi installation package
Gdebi- a program for installing .deb packages developed by Canonical specifically for Ubuntu.
Gdebi is not installed by default in Ubuntu, so you need to install it first, to do this, open a terminal and write the following line.
Sudo apt install gdebi
To install a local deb package use
Sudo gdebi package_version.deb
If there is a dependency issue, Gdebi will automatically install them for you, provided of course those dependency packages are available from the software repository.
Apt
apt (advanced packaging tool) is a program for installing, updating and removing software packages on Debian and Debian-based operating systems (Ubuntu, Linux Mint, etc.), sometimes also used in Mandrake-based distributions, such as Mandriva, ALTLinux and PCLinuxOS. Capable of automatically installing and configuring programs for UNIX-like operating systems, both from pre-compiled packages and from source code.
Typically you will use APT to install packages from online software repositories, as in this example:
Sudo apt install Firefox
Did you know that it can also be used to install local Deb packages? This is another reason why you should use apt instead of apt-get, which does not have this capability. You just need to go to the directory where the deb package is stored and install it as shown in the example below.
Cd/path/to/file/deb packages/ sudo apt install ./package_version.deb
For example, to install TeamViewer 12 on Ubuntu 16.04/16.10, first download the TeamViewer.deb package to your current directory
Wget https://downloadus1.teamviewer.com/download/version_12x/teamviewer_12.0.69753_i386.deb
Then install it with:
Sudo apt install ./teamviewer_12.0.69753_i386.deb
It automatically installs dependencies if those dependencies are available from the software repository.
When using apt to install local deb packages, you just need to add ./, which represents the current working directory, before the package name so that apt can easily find the deb package.
That's all!
I hope this post helped you install local Debian packages from the command line. If you found this post useful, please share it on social networks, and you can also subscribe to new news on the right side of the site.
You can install third-party software. For this, files with the .DEB extension are used. They are opened through the Application Center, terminal or utilities. The easiest way to do this is using a graphical interface. But users who have not worked in such an OS before are unlikely to be able to figure it out without instructions. On Ubuntu, installing a DEB package is a little different than running EXE files on Windows.
For the utility to work without errors, it is better to download it from the Linux Application Center (CPU). This way you will definitely receive the official software. It will update itself. You can search for files on the website of the developer of the program you need. Turn to unofficial sources as a last resort: for example, when your computer does not have Internet access. Also, manual installation of DEB is relevant if you do not find the utility in the CPU.
If the network is disabled on the computer, this is the only way to install drivers on it. It's better to look for them on launchpad.net. Type "Linux-Firmware" into the search bar. Next, select the distribution and architecture.
For a package to work, it needs libraries on which it depends. Such objects exist in other operating systems as well. For example, on Windows these are DLL files. When installing software from the Center, missing add-ons will be installed automatically. But with third-party utilities it’s not so simple. If there are no libraries and the CPU has not loaded them, then they must be downloaded manually.
GUI
The simplest thing is to install the DEB package via the graphical interface. It resembles Win Explorer. But there are still differences.
This is how you launch files through the App Center. It often slows down and opens utilities “incorrectly”. Therefore, it is better to use the console.
Terminal
Here's how to install a DEB package on Ubuntu using console commands:
Other utilities
There are other utilities for downloading installers.
Gdebi
If you don't have it, download it through the terminal. Enter the command “sudo apt install gdebi”. The service will appear in the files context menu. It's easy to use:
You can also use the console “sudo gdebi [Path_to_directory]/[Package_name].deb". The program itself will download the associated libraries if the computer is connected to the Internet and they are in the repository.
Apt
This is what installing DEB looks like on Ubuntu using the Advanced Packaging Tool. It is suitable for local packages:
- Launch Terminal.
- Go to the folder with the desired file “cd ~/[DirectoryName]”. You can specify the full path in the command.
- And type "sudo apt install ./[FileName].deb". A dot followed by a slash means you are accessing the current directory.
- Dependencies will be downloaded automatically if available.
Now you know how to install DEB package on Linux Ubuntu. There are many ways. You can download programs using an intuitive interface or terminal. Additional libraries on which the utility depends must also be downloaded. As a result, you will install not one package, but several.
- Extension (format) is the characters at the end of the file after the last dot.- The computer determines the file type by its extension.
- By default, Windows does not show file name extensions.
- Some characters cannot be used in the file name and extension.
- Not all formats are related to the same program.
- Below are all the programs that can be used to open the DEB file.
Universal Extractor is a convenient utility for unpacking various archives, as well as some additional file types. This program is primarily suitable for those users who create archives on a computer, but only download various archives from the Internet and then unpack them. The Universal Extractor utility copes with this task quite well. It allows you to unpack all known archives, as well as dll, exe, mdi and other types of files. In fact, the program can serve, to some extent, as a kind of program installer, because it allows you to unpack some of the installers and then run...
HaoZip is a Chinese clone of the popular Winrar archiver, both in terms of functionality and interface as a whole. The archiver can work with all popular formats, including 7Z, ZIP, TAR, RAR, ISO, UDF, ACE, UUE, CAB, BZIP2, ARJ, JAR, LZH, RPM, Z, LZMA, NSIS, DEB, XAR, CPIO, SPLIT, WIM, IMG and others. In addition, using Haozip you can mount ISO images and view images through the built-in viewer, which is a very useful feature for archivers. As for the interface, the Chinese developers have done a good job here. They not only copied the design and functionality from the Winrar archiver, but also added...
Peazip is a universal and powerful archiver with a graphical shell. An excellent replacement for its paid counterpart - Winrar. PeaZip supports data encryption, creating multi-volume archives, working with several archives simultaneously, exporting a task as a command line, and installing filters on archive contents. In addition, the archiver supports all known and even unknown archive formats including 7Z, 7Z-sfx, BZ2/TBZ2, GZ/TGZ, PAQ/LPAQ, TAR, UPX, ZIP and others. The PeaZip interface is very primitive and at the same time full of useful functions. You can use the assistant to integrate into Windows Explorer or return it back, install...
When developing the FreeArc archiver, the author decided to create a program that compresses files at maximum speed. This required the best qualities of the LZMA, PPMD and GRZipLib compression libraries. During the packaging process, the archiver forms files by type and performs compression using the most appropriate algorithm. When working, the archiver uses more than ten different algorithms and filters. If you compare this with common archivers, then 7-zip has only three, and RAR uses only seven algorithms. The archiver is easily adaptable for installation on various systems. It is developed on an open platform giving...
FileOptimizer is a convenient file compression application created by one of the independent teams of programmers. This application features improved compression algorithms and high speed. The program allows you to compress files of almost all types, including archives, text formats, image formats, etc. Also, this program can work with scripts, as well as through the command line, which will be especially useful for experienced users. For novice users, everything is very simple. The program is integrated into the context menu, which allows you to very quickly compress files located on any drive and in any folder.
TUGZip is a convenient archiver that has a clear user interface and also has a number of additional features. The TUGZip program allows you to work with almost all popular archives. However, the capabilities of the TUGZip program are not limited to this. The TUGZip utility allows you to work with optical disk images, for example, img, nrg, iso, etc. Also, the TUGZip program can be integrated into the context menu. But if most archivers only add submenus to it, then the TUGZip program boasts the ability to use various scripts to automate the process of creating archives, or decomposing them...
7-Zip is a well-known open source archiver. This feature allows you to make changes to the structure of the program, adding certain functions to it. The program has a clear and simple interface and has unique algorithms that speed up data archiving and unpacking. Also, this program can perform standard operations with the archive, for example, you can set a password for the file, or set the compression level of the archive. Also, if necessary, you can create a self-extracting archive with the necessary parameters, which are specified in special comments to the archive.
ExtractNow is a convenient program that allows you to unpack zipped files quickly: with just the click of a button. This option will be especially convenient for those users who regularly have to unpack many files. The only negative is that the program does not support creating archives, because... is exclusively an unpacker (high-quality and convenient), and not an archiver. To unpack a file, you need to drag the archives into the program window and click the Extract button. Supports popular archive formats. Thus, the program can unpack all the popular and most frequently used...
Simplyzip is a convenient archiver with all the necessary functions that most users use. The program works with almost all popular archive formats, including rar or zip. However, due to the fact that the developers of the winRar program do not allow the use of algorithms for their format, Rar archives can only be unpacked or their contents viewed. However, Simplyzip supports the installation of various modules and plugins that can expand the functionality of this archiver. If you install the necessary plugin, the program can be taught to create both Rar archives and archives of other formats...
Ashampoo ZIP is an archiver program that helps you compress and store the necessary information. Works with a variety of formats, allowing users to send large documents in a compressed form. Ashampoo ZIP has a wide range of different functions. Using the application, you can create, unpack and split archives. In addition, the program supports reading, recovery, encryption, and instant conversion. The list of formats supported by Ashampoo ZIP is quite impressive. In addition to creating archives, the program supports unpacking documents in more than 30 different archive formats.
IZArc is a convenient program for working with archives, featuring a clear and simple interface, as well as a number of additional features. IZArc supports a huge number of formats, including the most popular rar and zip. Unique algorithms used in the program allow you to increase the speed of working with archives. However, the main feature of IZArc is that it can easily convert archives from one format to another. This is especially necessary if you need to transfer some files to another user who does not have the appropriate archiver. In addition, IZArc allows you to view...
Every year, to improve and enhance the convenience of users, developers of various computer software release many interesting, convenient and high-quality programs that significantly help in their work. One of these programs is the latest development of the WinArc archiver. This utility is available for public use and with its help you can easily archive or unarchive any file that interests you. During operation, this utility uses all processor cores, thereby speeding up the archiving process. In addition, it has the function of adjusting the use of RAM, which will significantly reduce the load on your computer...
DEB file- is an installation file for Linux OS, for example in Debian or Ubuntu (as in Windows or .pkg on Mac OS), so you don’t need additional programs to open it, just double-click on it and it will start.
BUT! If you want to run this file without having a computer running Linux OS, you can use the program. To simply extract files (not launch), you can use any archiver, for example WinRar...
Extension .deb What is the file format?
File Format.deb indicates that this file contains an installation package for the Debian, Ubuntu and other operating systems built on Linux. The Debian operating system is free software with source code, and is currently one of the most popular Linux distributions.
The installation package for the Debian operating system is nothing more than an archive file, which is compressed using the RAR archiver, which has found its use in Linux systems, and contains two files. The first, of which is service information, and the second is packaged software
History of Debian OS:
This operating system is not as popular as Windows, but it has a number of advantages, which is why many users choose it, since in some cases it can be much more productive, and it is practically not susceptible to virus attacks, since there are practically no viruses for this system. does not exist. Also, this system and others like it are very frequent guests on various servers.
In operating systems of this type, installation can occur in two ways, the first of which is to compile the application from source files that contain the program code. The second method involves using binary packages.
Now you know how to open deb and what programs to use for this!