bkcvs 0.2.1 (2002-02-20)
Build KDE from CVS
Copyright (C) 2001, 2002 by Roland Riegel <support@roland-riegel.de>
- Introduction
bkcvs helps you to simply download the current KDE developer sources from the CVS repository and to compile them without any user interaction. It automatically manages the local source copy in a directory of your choice and asks for several other options concerning your future KDE CVS install. For example you can specify what GUI languages you want to use or in what file bkcvs should log its activities to.
2. Installing / Compiling bkcvs
You do not need to compile or install bkcvs as it is a bash shell script.
Of course you can also copy the script bkcvs to /usr/sbin or whatever is in your $PATH. Pay attention to the permissions of the script and that only you can execute or edit it.
Before running bkcvs, please read the following chapter!
3. Using bkcvs
Before running bkcvs, make sure there is a file named bkcvs.pkg in the current working directory. This file contains the names of the packages you want to build from the KDE CVS repository. If you do not want to build a listed package, put a '' as first character of the line in front of the package. The other way round remove the '' if you want to compile a package. Do not forget to save the file! ;-)
PLEASE NOTE: You always need the packages kdelibs and kdebase for a running KDE! If you do not have already a current version of QT on your system, please also compile the package qt-copy.
The order of the packages in the bkcvs.pkg file is the order the packages will be downloaded and compiled. So please never reorder qt-copy, arts, kdelibs and kdebase as they depend on this order.
For an example bkcvs.pkg file look into the directory where this README is.
If you finally have prepared the bkcvs.pkg file for your needs and you have made sure you are connected to the Internet, simply run ./bkcvs
You will be asked some questions about your KDE CVS install. The answers will be saved in the file ./bkcvs.cfg. This file is read when bkcvs starts up. You do not need to answer the questions every time you want to build KDE. Edit the file if you want to change some of your answers or simply delete it for being asked the questions again.
After having answered the questions, bkcvs starts downloading and compiling each package. Being asked for a password, simply press Enter. If a package fails to compile, bkcvs cleans all files in the package directory except the ones from CVS and restarts the compiling process. If it fails again, bkcvs gives up and proceeds with the next package.
You can also run bkcvs with the command line switches -c or -d (not both). The switch -d tells bkcvs to only download the CVS source code, -c does only the compilation. Please do a bkcvs --help for further information.
PLEASE NOTE: On my Celeron 466 with 192 MB RAM it lasts (without downloading) about 12 hours to build a pretty complete KDE! So please be patient!
It is always a good idea to look into the bkcvs log file created by bkcvs during downloading and compiling.
4. Uninstalling bkcvs
If you have not copied any files like described in chapter 2, there is
nothing to uninstall. ;-)
Else delete the file bkcvs from your directory in $PATH and the files
./bkcvs.cfg and ./bkcvs.pkg.
5. Copyright / License
Copyright (C) 2001, 2002 by Roland Riegel <support@roland-riegel.de>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.