Debian Package Management, Part 1: A User's Guide
Gnome-apt is a GUI package manager for Debian built around Gnome. It is incredibly intuitive and can be quite useful. Gnome-apt displays package sizes, dependencies and just about any other relevant information in a well laid-out interface. The packages are presented in a sorted tree (see Figure 2), and gnome-apt can display packages broken down alphabetically or by section, status or priority. It also has easy and powerful search functionality. Gnome-apt is included in Debian 2.2 (Potato) and the current unstable distribution (Woody).
KPackage is the KDE package front end for both RPM and Deb. It uses a combination of tabbed and tree interfaces (see Figure 3), and the functionality is similar to gnome-apt. One of the cool features of Kpackage is that the dependencies are hyperlinks to the packages they reference. Kpackage also lists the files included in each installed archive and checks to make sure they all exist. It can be found at http://www.general.uwa.edu.au/u/toivo/kpackage/.
console-apt is a new front end just for APT. Currently, it is only available in the unstable distribution of Debian; as it is still in development, I won't say too much about it. Console-apt does have some nice features, though, including a much more intuitive and usable interface, progress indicators for downloads, selective upgrades and the ability to search, sort and filter the package listings.
Using these options and features, you should now be able to maintain and manage your Debian package system with ease. Trust me, it sounds more complicated than it actually is. I've tried to provide as many options as Debian offers but had to leave some out; I have not yet been able to pry myself away from APT. In conclusion, I haven't seen any RPM front end that I feel is on the same level as APT.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- Home Automation with Raspberry Pi
- Huge Package Overhaul for Debian and Ubuntu
- The Controversy Behind Canonical's Intellectual Property Policy
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development