| dropline GNOME | |
| Screenshot Size: | 250px |
| Author: | Todd Kulesza |
| Developer: | dropline GNOME Development Team |
| Released: | 2002[1] |
| Latest Release Version: | 3.20 |
| Latest Release Date: | [2] |
| Latest Preview Version: | 3.20 RC1[3] |
| Programming Language: | C Language |
| Operating System: | Slackware |
| Genre: | Desktop |
| License: | GNU GPL and others. |
Dropline GNOME is a version of the GNOME desktop environment intended for use in Slackware. As Slackware has not included GNOME since 2005, Dropline GNOME is an option for Slackware users who wish to use GNOME as their desktops.
Dropline GNOME 3.20 was released on December 31, 2017.[2]
Due to developer constraints, the version of GNOME included with Slackware was inferior to that of many other distributions, and was later dropped entirely from the distribution.[1] Dropline GNOME was created to account for the shortcomings and to fill the void left by this decision.
Todd Kulesza, dropline GNOME's founder, has retired from further work on it. Dropline GNOME is now being maintained by a small group of volunteers from around the world who build different parts of the system.
Each minor (second version number) release of GNOME results in a new installer application and package group being released. However, subsequent micro (third version number, e.g. from 2.16.1 to 2.16.2) releases of GNOME are typically distributed in the form of individual package updates as source packages are updated, and do not require replacement of the installer package. To ensure that users do not easily fall behind in package updates, Dropline GNOME includes a panel applet to notify users when new packages for their installed release are available for download.
Dropline GNOME has been criticized by some, including Slackware creator Patrick Volkerding, for adding PAM to the system, and for replacing large system files, including the whole X11 system.[4] However, the Dropline GNOME team has discontinued rebuilding X11 as of version 2.16.1. They use the official Slackware packages whenever possible, and publish a list of conflicting packages for each targeted Slackware system/release.
Cases such as the PAM addition are not done without merit, however, as pam_console is an essential component in providing functional automount support via HAL, the GNOME Volume Manager, and other software.