Compile.conf

Compile.conf is the file where you can configure the various paths and URLs used by Compile.

It is stored at /Programs/Compile/Settings/Compile/Compile.conf – which, once installed, has a link at /System/Settings/Compile/Compile.conf (if you’re used to the GoboLinux tree, you should know by now that this is the same as /etc/Compile/Compile.conf).

These are the usual contents of the file:

Your name here so that credit is added to recipes.

compileRecipeAuthor="Paul McCartney"
# example only! change the name (unless of course, you're Paul ;) )

The standard locations for your local Compile files.

compileArchivesDir="$compileDir/Archives"
compileSourcesDir="$compileDir/Sources"
compileRecipeDirs="$compileDir/Recipes"

Some of the main free software repositories are treated especially: recipes use these variables in their url declarations, so that you can pick your favorite mirror without having to edit recipes one by one:

ftpGnu=ftp://ftp.gnu.org/gnu/
ftpAlphaGnu=ftp://alpha.gnu.org/gnu/
httpSourceforge=http://unc.dl.sourceforge.net/sourceforge/

The Compile recipe tree is managed by Git. The git repository and the upstream branch are both configurable through the following variables:

compileRecipesRepository=https://github.com/gobolinux/Recipes.git
compileUpstreamBranch=master

A variable to set the make command called by Compile. ColorMake provides the highlighting that GoboLinux has by default:

compileMakeCommand="ColorMake"

Options to use with the make command. This can be used to run multiple threads in parallel on different CPUs or for other customisation:

compileMakeOptions="-j2"

Environment variables

Some environment variables influence the behavior of some GoboLinux tools. You may want to set them. Just remember that GoboLinux uses zsh (not bash) as its default shell, so you should edit .zshrc (not .bashrc). Zsh is a Bourne-style shell, though, so the syntax you’re used to is still valid.

Of course, if you really prefer bash (though we really recommend giving zsh a try!), you can change your default shell using the chsh command. See the chsh man page for details.

The $EDITOR variable should be set to your favorite text editor. Whenever a GoboLinux tool needs to run an editor, it will run the one indicated in this variable (in fact, this is not a GoboLinux variable, several programs use it).

GetAvailable

GetAvailable.conf is the file where you can configure paths and URLs used to locate binary packages.

It is stored at /Programs/Scripts/Settings/Scripts/GetAvailable.conf – which, once installed, has a link at /System/Settings/Scripts/GetAvailable.conf (if you’re used to the GoboLinux tree, you should know by now that this is the same as /etc/Scripts/GetAvailable.conf).

These are the usual contents of the file:

The timeout (in seconds) when trying to fetch the packages list from a sever.

timeout=15

The paths from which local packages will be automatically be found. Notice that both compressed (e.g. /Depot/Packages/Qt--4.0.0--i686.tar.bz2) and uncompressed (e.g. /Mount/SquashFS/Programs/Qt/4.0.0) packages can be matched.

defaultLocalPackagesPaths=(
"/Depot/Packages"
"/Mount/SquashFS/Programs"
"/Mount/CD-ROM/Depot/Packages/"
"."
)

The URLS from which lists of official binary packages (packed by some core developer) will be retrieved.

officialPackagesLists=(
'http://kundor.org/gobo/packages/official/MANIFEST.bz2'
'http://gobo.calica.com/packages/official/MANIFEST.bz2'
)

The URLS from which lists of contributed binary packages (contributed by some user, and placed, without garanties, at our servers) will be retrieved.

contribPackagesLists=(
'http://kundor.org/gobo/packages/contrib/MANIFEST.bz2'
'http://gobo.calica.com/packages/contrib/MANIFEST.bz2'
)

The URLS from which lists of tracked versions will be retrieved. A tracked version is a program version that actually may not have a correspondent Recipe or binary package, but that is already made available by the program developers

trackedVersionsLists=(
'http://gobolinux.org/version-tracker/TrackedVersions.bz2'
)