By default, the most recent sources are used when installing, so testing is used in preference to stable, and unstable is used in preference to testing. If you want packages from contrib or non-free, you will need to add the sections to each source in a text editor, then run apt update to enable the new sources. Shown here is the start of the reverse dependencies for gcc – which are so numerous that gcc is a poor candidate for mixing because the chances are high that something can go wrong.ĭebian systems install from the repositories list in /etc/apt/sources.list. As well, you might use the option -no-install-recommends and avoid -install-suggests to keep the mix as simple as possible.įigure 2: F2_rdepends: It is often useful to see which other packages depend on the one you are going to mix. You might also run apt-get-simulate install PACKAGE or even try a proposed action in a virtual machine first. The command apt-cache rdepends PACKAGENAME will show the other packages that use a dependency, indicating the possible extent of any consequences – although not all packages react the same way (Figure 2). The best odds for successful mixing are packages with no dependencies or no shared ones. If you don't know what a dependency does, take the time to learn. As a rule, the more dependencies or the more important the dependencies, the greater the risk. In particular, pay attention to the dependencies updated with testing and unstable packages. If you must mix, take the verbosity of apt-get/apt seriously. For any of these reasons, mixing will happen. ![]() ![]() Besides, occasionally a bug occurs in stable and the quickest fix is in testing and unstable. Besides, Debian-derivatives borrow from testing and unstable all the time, which gives the illusion of safety, if you overlook the additional testing the derivatives do. Sometimes, that means that its apps lack a needed feature. Many users crave the latest apps, and while stable may be reliable, it can be several releases behind the latest applications, especially near the end of the general release cycle. Still, let's face it: Users will mix repositories despite any warning. The repository names alone are a warning –especially if you venture beyond the three basic repositories to others such as the experimental repository. If any of these misfortunes occur, you have only yourself to blame. Too often, a reinstall is the quickest solution. A single careless step, and you could lose your desktop environment, the ability to work with packages, or some other basic part of the installation, and find yourself condemned to hours of futile efforts to recover. But set up the testing and unstable repositories intended primarily for developers, and nothing is guaranteed. Stay with stable and you enjoy the full support of the distribution, including backports and security updates. By default, a Debian system enables only the stable repository. This second axis is the main Debian repositories themselves. Only the stable and testing repositories are listed. Note that the cdrom used to install is disabled by commenting out, and that all three sections of repositories are listed. ![]() Figure 1: F1_sources-list.png: The sources.list file contains the addresses of all repositories used by a Debian system.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |