This is an introduction for real beginners of source installation. If you are already somewhat experienced with UNIX-like systems and GNU source code install procedures, you should skip this chapter, otherwise
sourceinstall will try to make configuration, compilation, installation and removal of source packages easier for you as a beginner.
Instead of hiding information and operations from you, everything that happens will be available for you to see.
This way, if you are interested you can hopefully understand basic concepts by just looking at the commands executed by this program in the information frame.
Provided your system meets the requirements, and thus you manage to have a working installation of sourceinstall itself, you will be shortly able to install new software from its source code by surfing the web, identifying a Free Software you like, downloading its SOURCE package, and feeding it to GNU Source Installer.
If you have a fast internet connection, proceed to download sourceinstall-0.5-fullpack.sh or a newer version, and mark where the file will be placed (the “folder”, the directory). You must have the permission to write in that directory. For example, we will assume that you are downloading to
After the download completes, start a console session. Your desktop environment should include a button, picture, or menu item that refers to a “shell”, “terminal” or “console”.
After the console is open, you should see a brief message ending in $; this message will be represented here by a single dollar character, and you shall NOT type that character as part of the commands.
Reach the directory you just downloaded your file in, by typing in the shell this command, followed by a RETURN:
$ cd /home/user/downloads
where of course /home/user/downloads is the directory in which you downloaded the file.
If you get an error message, double check your command for typos. If things are going well, you will know because you will get nothing else than another $ ended message (a prompt).
At this point, you can decide if you want to install as the super-user (root), or using your ordinary account.
Installing as root is more indicated for system-wide installs. To do so, type
$ su (Enter your root password)
At this point run the installer by typing:
$ /bin/sh sourceinstall-0.5-fullpack.sh
wait for the package to extract (this might take some minutes on slow or loaded systems), and follow the instructions. After being asked some simple questions, hopefully you will get a working installation of the GNU Source Installer. Mark the executable name that is showed at the end of the procedure, because that is the program that you need to run to start the installer.
This setup procedure installs in a subdirectory of your home directory by default if you are using an ordinary account. In particular, by default the installation prefix (the directory subtree in which to install) is ~/usr, where ~ represents your home directory.
If you are using a root account, then the setup procedure will instead use /usr/local as the default prefix. This is a common prefix for system-wide installs.
If you have a fast internet connection and want the easiest install, you can skip the rest of this section, and jump to the “Troubleshooting” section if you experiece any problems during installation.
If you are a bit more daring, instead, you can try a normal source release.
The releases whose names end in -fullpack are many megabytes in size, because they contain all the major dependencies in source form, and it could be that you already have the required packages.
You can fetch the much smaller sourceinstall-0.5.tar.gz (or other version). We will assume the same destination directory as above for the download.
At this point enter the following command (this assumes you have the GNU version of tar):
$ tar -zxvf sourceinstall-0.5.tar.gz
or, if you do not have the GNU version of tar (f.e. Solaris):
$ gunzip sourceinstall-0.5.tar.gz $ tar -xvf sourceinstall-0.5.tar
Note that you can use the tabulation (TAB) character to complete names. Experiment with pressing (TAB) around the middle of the file name.
All the files you'll see are being extracted from the archive, and a new directory is being created in the current one. At the end type:
$ cd sourceinstall $ ./configure
A lot of output will be showing at this point. The software is being configured (adapted) for your system. If everything runs smooth, you will see at most WARNINGs but no ERRORs. After a while you will get the familiar dollar, and now you can write:
Some output will be shown, then again the familiar prompt. And now:
$ su (Enter your root password) # make install
su, you will be asked for your root password.
You should have set your root password during your Operating System initial setup. If you do not know, try pressing ENTER.
The # character before
make install denotes the fact that after
su you have gained root privileges. Since you are done, drop your root privileges by typing
Each time you want to run GNU Source Installer from the console, type:
To run it from the graphical environment, you should create some kind of “shortcut” or “link” to the program on your desktop or in your program menus. The program to launch is (assuming a root installation and default values) /usr/local/bin/sourceinstall .
If you experience errors that prevent the correct installation and execution of the program, the next section tries to deal with these cases.
At the end of the procedure you will get the following files installed:
To consult the GNU Source Installer manual type
$ info sourceinstall
If you want a brief overview of program invocation and options, you can consult the traditional man page by issuing
$ man sourceinstall
If you could not install GNU Source Installer, this is most likely because you do not have the required software in your system. In other cases, it could be a bug in the installation procedure.
For the -fullpack releases, it is most likely the second (the special -fullpack release is meant to install without dependency errors).
If you need to report a bug that prevented the correct installation of a -fullpack, please provide all the files ending in .log and .err that are generated during the procedure.
To find all these .log and .err files, after getting the error during installation, look in the directory in which you ran the procedure. In our example, it was:
You should find a sourceinstall-fullpack directory there. It is a directory created during installation, that is removed after the operation and only if it completed correctly. In your case, if you have an error during the procedure, the directory will still be there. That directory should contain many files whose names end in .err and .log . These are the files to attach to your bug report. As always, report your bugs to firstname.lastname@example.org .
If you are using a normal release (not a fullpack), look at the output of
./configure, instead, and you will see if some needed programs have not been found on your system.
The most blocking thing is if you miss tcl, Tk or Expect: in this case
./configure will exit with an error, and make will not be able to run.
If this is your case, you will need to install tcl, tk and/or expect (or try the -fullpack release instead). If you have your OS installation disk(s), chances are that the software is available there, and is installable using the OS specific installation system.
Otherwise you should fetch and build the Tcl, Tk and Expect source packages. You can fetch Tcl and Tk from http://sourceforge.net/projects/tcl/, while Expect is available at http://expect.nist.gov/ . They are a bit tricky to install, so if you cannot find your way out of them, you can always revert to the -fullpack release.
If you succeed in building a working Tcl/Tk/Expect environment, restart the procedure from
./configure and things should be better.
If you miss any of the other helper programs, only the particular functionality offered by that program will be missing (a WARNING will be shown).
This is a comprensive list of programs that GNU Source Installer uses, from the most important ones, to the really secondary:
If you still have problems, you can write an email to the sourceinstall users mailing list email@example.com and ask for help. Something that can help a lot is reporting the full output of
Feedback of any sort is also welcome. Good luck, and I hope this helps :)