KBFX – an alternative to T-Menu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

INSTALL 6.6KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203
  1. ############################################
  2. # #
  3. # INSTALL file for KBFX > 0.4.9.2 #
  4. # #
  5. ############################################
  6. Last update: 03/03/2007
  7. Installation Notes by PhobosK
  8. 1. Requirements :
  9. =================
  10. - Cmake ( http://www.cmake.org ) - min. version 2.4.2
  11. - KDE3 and Qt3 sources - header files/devel packages
  12. - Strigi ( http://strigi.sf.net ) - header files/devel packages needed too
  13. (optional package)
  14. 2. Compilation Instructions :
  15. =============================
  16. 2.1. Unpack the sources of KBFX with (x.y.z-XXXXXXXX represents the version of
  17. the KBFX package, for example : 0.4.9.3-20070117):
  18. > tar xjvf kbfx-x.y.z-XXXXXXXX.tar.bz2
  19. 2.2. Change into the new directory:
  20. > cd kbfx-x.y.z-XXXXXXXX/
  21. 2.3. Start the configuration and the compilation using the command:
  22. > ./build.sh
  23. Note for Mandriva < 2007 users:
  24. ===============================
  25. The build script (by default) enables the use of "menudrake"
  26. instead of "kmenuedit". If you want to prevent this behavior then
  27. pass ONE of these options to the build script:
  28. "--menudrake-off" OR "-m"
  29. Notes for other building options:
  30. =================================
  31. "--prefix" OR "-p" to install KBFX in a different than the default folder
  32. (default is KDE install folder) for example:
  33. > ./build.sh -p /home/user
  34. "--strigi" OR "-s" to enable Strigi support in KBFX
  35. (default is no Strigi support)
  36. "--kde4" OR "-k" to build KBFX for KDE4
  37. (default is for KDE3)
  38. "--verbose" OR "-v" to make the build script give more verbose information
  39. "--nocheck" OR "-n" to make the build script not to check if an old KBFX
  40. version is installed (default is to check)
  41. 3. Using the "checkinstall" application for building KBFX packages :
  42. ====================================================================
  43. "checkinstall" DOES NOT work with cmake correctly up to this moment. :(
  44. It can be used with additional commands in order to "work properly".
  45. Here is the procedure to follow as user (NOT as ROOT) in order to obtain
  46. the necessary distribution package.
  47. NOTE: - x.y.z-XXXXXXXX represents the version of the KBFX package,
  48. in this example it is: 0.4.9.3-20070117
  49. - in the example here the version string is replaced only in the
  50. checkinstall comand but you have to do that everywhere the
  51. "x.y.z-XXXXXXXX" string is met
  52. > cd /tmp
  53. > tar xjvf kbfx-x.y.z-XXXXXXXX.tar.bz2
  54. > cd kbfx-x.y.z-XXXXXXXX/
  55. > mkdir -p build/package
  56. > cd build
  57. > export DESTDIR=/tmp/kbfx-x.y.z-XXXXXXXX/build/package
  58. > cmake ../ -DCMAKE_INSTALL_PREFIX=`tde-config --prefix`
  59. > make install DESTDIR=/tmp/kbfx-x.y.z-XXXXXXXX/build/package
  60. > find package/|sed s#^package/#./# > installed_files.txt
  61. > cd package/
  62. > su
  63. > checkinstall -nodoc --pkgname="kbfx" --pkgversion="0.4.9.3" --pkgrelease="20070117" \
  64. --exclude="/" --include=../installed_files.txt --pakdir=/tmp/kbfx-0.4.9.3-20070117 sleep 1
  65. When ready, "checkinstall" will show you the folder where the prepared package
  66. is, like in this Mandriva Example:
  67. **********************************************************************
  68. Done. The new package has been saved to
  69. /tmp/kbfx-0.4.9.3-20070117/kbfx-0.4.9.3-20070117.i386.rpm
  70. You can install it in your system anytime using:
  71. rpm -i kbfx-0.4.9.3-20070117.i386.rpm
  72. **********************************************************************
  73. Of course the best way to make RPM packages is to use the "kbfx.spec" file provided
  74. in the KBFX sources like described bellow.
  75. 4. RPM Building Instructions (Mandriva, Fedora, Suse) :
  76. =======================================================
  77. If you prefer manipulate a RPM, you can build it with the following commands:
  78. 4.1. Build the RPM
  79. > rpmbuild -tb kbfx-x.y.z-XXXXXXXX.tar.bz2
  80. or (for Mandriva)
  81. > rpmbuild --rebuild kbfx-x.y.z-XXXXXXXX-mdv20070.src.rpm
  82. or (for Fedora)
  83. > rpmbuild --rebuild kbfx-x.y.z-XXXXXXXX-FCx.src.rpm
  84. or (for SuSe)
  85. > rpmbuild --rebuild kbfx-x.y.z-XXXXXXXX-suseXXX.src.rpm
  86. 4.2. If succeed, you will found the rpm in /usr/src/rpm/RPMS (for Mandriva)
  87. or /usr/src/redhat/RPMS (for Fedora) or /usr/src/packages/RPMS (for Suse)
  88. according to the platform you have.
  89. 4.3. Install the rpm as usually by:
  90. > rpm -Uvh kbfx-x.y.z-XXXXXXXX.rpm
  91. Notes for building RPM from KBFX SVN versions :
  92. ===============================================
  93. - Follow these commands in the sources directory:
  94. > ./build.sh
  95. > Answer "N" to the question if you want to install KBFX
  96. > cd build
  97. > make dist
  98. - A file "kbfx-x.y.z-XXXXXXXX.tar.bz2" will be created in the build
  99. directory.
  100. - Proceed with the steps described in 4.1., 4.2., 4.3.
  101. 5. Gentoo users:
  102. ================
  103. In order to use the strigi engine in KBFX you have to do these steps:
  104. - Copy the "strigi-X.X.X.ebuild" and the "kbfx-0.4.9.X.ebuild" (from the sources
  105. directory) to your local portage tree as needed
  106. OR use the "kbfx-0.4.9.X-portage-overlay.tar.bz2"
  107. - Set the flag "strigi" for the kbfx ebuild
  108. - Emerge "clucene"
  109. - Emerge "kbfx"
  110. There is a Layman overlay resource on the SourceForge SVN.
  111. You can add it by this command:
  112. > layman -f -o https://kbfx.svn.sourceforge.net/svnroot/kbfx/layman/kbfx-overlay.xml \
  113. -a kbfx
  114. After you add the "kbfx" overlay you can use it as usual.
  115. 6. Getting SVN version:
  116. =======================
  117. To download the latest development source, you need to go to KDE SVN
  118. and download it from there. The current SVN address of the repository is:
  119. svn://anonsvn.kde.org/home/kde/trunk/playground/base/kbfx_plasma
  120. Here are the instructions on how to get a copy of the SVN Repository:
  121. 6.1. Install your distribution's package named "subversion"
  122. OR download and install it from: http://subversion.tigris.org
  123. 6.2. Create a folder where you will compile/install KBFX and enter in it.
  124. For example do this:
  125. > mkdir -p ~/usr/src/svn
  126. > cd ~/usr/src/svn
  127. 6.3. Checkout the SVN version of KBFX in this way and proceed as follows:
  128. > svn co svn://anonsvn.kde.org/home/kde/trunk/playground/base/kbfx_plasma
  129. > cd kbfx_plasma
  130. 6.4. Proceed with the compilation/installation of KBFX as described in 2.3.
  131. > ./build.sh
  132. 6.5. If you want always to have the latest version of KBFX you may leave
  133. the folder ~/usr/src/svn/kbfx_plasma intact for future use.
  134. When you want to update the source files of KBFX you just need to do
  135. "svn up" in this folder, delete the folder ~/usr/src/svn/kbfx_plasma/build
  136. and do the step described in 2.3. i.e:
  137. > cd ~/usr/src/svn/kbfx_plasma
  138. > svn up
  139. > rm -fR build
  140. > ./build.sh