This wiki is dedicated to the management and documentation about our build system. We provide our full build system, that is to say, it is the full and complete GSB source code we use to generate our binary distribution. It is a collection of SlackBuild scripts that build a GNOME release on Slackware Linux. The build system also comes with a download script to grab all the latest source tarballs for every package that GSB can build.GSB distribution from the actual GSB source code. It is recommended that you read through (and even print) this entire document before starting the build process. It covers topics about how to check out our source from git, download the source tarballs, customize your build settings, and run the build. This master branch version of GSB is designed to build packages using:
If you are trying to build GSB on systems other than the above you will encounter problems during the build.
We have other branches in the code repository for other GSB and Slackware versions. The branch naming conventions are self-explanatory.
We cannot offer any form of support to users trying to build GSB on earlier versions of Slackware or Slamd64. However, if you do manage to get GSB built on other versions, please let us know what modifications you had to make to the build system in order to do so – if those changes can be integrated into our build system, you may find those versions supported out of the box in our future releases.
The developers use a strictly controlled base of packages to build the binary packages for the project – we only install the minimum packages required to perform a build. We work from a set of ‘tagfiles’ which specify exactly which packages get installed into our build environment. We have included our tagfiles set in the tagfiles/ directory in our git tree for reference.
When it comes to building your own packages, it is doubtful your build will succeed if you do not have every package marked with an “ADD” in our tagfiles installed on your system. Those packages marked “ADD” form the basis of our build requirements – any missing packages from your system will likely cause the build to fail. If you have a full installation of Slackware or Slackware64 you should not have any problem doing a build, but the resulting packages may have more dependancies than indicated in our slack-required files (because many of the sources will find extra libraries when being configured and automatically link against them).
Unless you really know what you are doing with packages, understand what tagfiles and dependancies are all about, and really feel the need to “roll your own”, it would be a far far better choice for you to download the pre-built binaries and install those.
For the brave, please find more information about the Build System, please see our Building GSB page.
This page contains some useful information for people who want to start work developing the GNOME SlackBuild source. We are always looking for volunteer help to any aspect of GNOME SlackBuild, whether it be coders, documentation writers, bug finders, graphic designers, web folks, etc. On this page you will find information about our mailing lists, our ChangeLogs. information about our repositories (both source and binary), our RoadMap, and our TODO list.
For more information for interested developers, please see our Development page.
The preferred method of reporting bugs is through this very system (click “New Issue” on the top!). Firstly, check the issue archive to see if anyone else has had a similar problem which has already been solved. You will not get any points for requesting help with a problem that has already been addressed.
Last edited by Chip Cuccio,