Skip navigation.

GNOME SlackBuild RC1: GNOME 2.20.3 Desktop for Slackware 12

GNOME
GNOME

Originally based on the Freerock GNOME project, GNOME.SlackBuild (GSB) provides the latest GNOME Desktop (2.20.3) for Slackware Linux. It includes both a binary distribution, as well as a complete GNOME source build system. The GSB project has been re-vitalised by a new development team who have, over the past several months of hard work, re-engineered the GSB source build system and brought the project back to the forefront of the GNOME packaging projects for Slackware. This project also supports and provides binary packages for x86_64 ports of Slackware, such as Slamd64.

For information about the project, screenshots, and downloads, please see http://gnomeslackbuild.org

use the right tool!

linux offer an incomparable freedom to customize your software, it's a fact... well, when you customize something you must (usually) know what you doing, and sometime even after knowing this, something goes wrong (or not exactly in the way you expected ;-)

Distributions and packaging systems are created to make things in a specified way, and customize software in a consistent manner, providing help support that can be useful mainly thanks a quite "reproducible" environment.

What i've learned after some years of daily linux usage and crossing various distribution (from red-hat, mandrake, slack and gentoo now) is that it's always better (IMHO) use the tools that your distribution offer to you, to install and configure your system.

I'm used to customize my software starting from the source code level, i've done it for almost an year using slack, learning really a lot of things (thanks!), but at the cost of too much efforts and wasted time to obtain, at the and, an hybrid system sometime not so reliable like i wanted.
I know it's my fault, but am i alone at this world? No! what's open-source or free software without sharing information experience and work?

What i thing is that if you want to build from source an entire desktop system (like i done with slack), and you consider it a very important piece of software for your daily work, probably you want to build all, or a lot of, others software.

So why use slack to do this? Slack it's a very reliable, proved, and, in some ways, maybe the latest easy "human understandable" distribution, but it's done with binary tarball in mind not for rebuild itself.

I don't mean that there's something wrong develop a GNOME source build system like this (they are always welcomed in helping upstream) but, looking at my experience, i feel the need to "warn" users that it's better to use a right tool (or distribution in this case) explicitly created to build things from source if they needs this level of customization.

Thanks for read thus far ;-) bfx81