Installation In order to successfully use the most recent &krusader;, you need &kde;libs >= 3.4 Required &kde; version: &krusader; v1.01: &kde; 2 &krusader; v1.02 - 1.40: &kde; 3.0 - &kde; 3.2 &krusader; 1.40: prefers &kde; 3.2 (otherwise all features will not be available) &krusader; v1.50 - v1.51: &kde; 3.2 - &kde; 3.3 (Konfigurator crash on &kde; 3.4) &krusader; v1.60.0 - v1.70.0: &kde; 3.3 - &kde; 3.5 &krusader; 1.70.x: prefers &kde; >= 3.4 (otherwise all features will not be available) &krusader; 1.80.0: &kde; 3.4 - &kde; 3.5 &krusader; v2.xx.x: &kde; 4 - &Qt; 4 The big challenge, a first release in 2008 NOTE: there are no installation instructions for &kde;4 yet available since at moment of writing &krusader; was not ported yet to &kde;4. Platforms: All POSIX (&Linux;/BSD/&UNIX;-like OSes), &Solaris; All BSD Platforms (&freebsd;/&netbsd;/&openbsd;/&MacOS;) &krusader; uses about 3-4 Mbyte of memory to run and about 15 Mbyte of shared memory, which is also used by other processes, but this may vary depending on your platform and configuration. In order to handle archives the archivers must be configured here. A package of popular (un)packers, &krusader; itself and add-ons can be found on the &krudownload-url;. For more requirements, see below. Have a look at the &faq-lnk; section as well. The latest information about &krusader; can be found on the &kruwebsite-url; . it is recommended to use the &krusader; package that is provided by your distribution. &distrowatch-com-url; is a great resource to check the availability. If your distribution does not offer &krusader;, please contact the creators of your distribution and ask them to provide a &krusader; package The latest version, as well as the older versions, can be found on the &krudownload-url; and on the &sfmirrors-url;. It contains the source tarballs, RPM and DEB packages to whatever distro the &krusader;-Krew is using and packages build by &krusader; users and third parties. Distributions who provide &krusader;: &suse-download-url; >= 9.3, Note: please use &krusader;-1.60.0 instead of &krusader;-1.51 (might be unstable on &SuSE;9.3-&kde;3.4). &fedora; via &fedora-extras-url; # yum install krusader will do the job, thanks to Marcin Garski. &RedHat; RPM packages can usually found on the &krudownload-url; or at &dag-wiers-download-url; and &dries-verachtert-download-url; . &debian-download-url;, on our &krudownload-url; you might find more recent DEB packages. Note: usually &debian; packages work also on distributions that are "based on &debian;", and some of these provide their own (incompatible) packages. &ubuntu-kubuntu-download-url;, &linspire-download-url;, &knoppix; 4.x DVD, &kanotix;, etc. &mandriva-download-url; via the contrib repository # urpmi krusader will do the job, &gentoo-download-url;, &yoper-download-url;. &archlinux-download-url;, &frugalware-linux-download-url;, &pclinuxos-download-url;, &altlinux-download-url;. &freebsd-download-url;, the port is maintained by Heiner Eichmann. &netbsd-download-url;, &lunarlinux-download-url; ,&arklinux;, &openlx;, &sourcemage;. Even more distributions can be found with &distrowatch-com-url;. Use the installation tools included in your distro to install the &krusader; package. You might need an internet connection if &krusader; is not included on the &CD; or DVD. There are probably other distributions which include &krusader;. If you know of one, please send feedback so that we can include it on the distrolist. Others &slackware; tgz binaries can usually be found on the &krudownload-url;. You can also use &portpkg-url; that contains a &kru-slackbuild-url;, # portpkg krusader will do the job. There is a &macosx-port-url; with the help of &fink-url; , the port is maintained by Catalin Hritcu. Installation via the &klik-protocol-url; &klik-krusader-url; downloads &krusader; provided by &debian; stable, more information is &klik-available-url; . &klik-krusader-latest-url; downloads the latest &klik-stable-krusader-url; provided by the &krusader; Krew. &klik-krusader-cvs-url; downloads a &klik-cvs-krusader-url; provided by the &krusader; Krew. Search engines You can also find packages on &Linux; software archives such as &freshmeat-url; or &kde-apps-url; . If you can notfind a package for your distribution, we recommend searching for it with &rpmfind-url;, &rpmpbone-url; or &rpmseek-url;. If you enjoy using &krusader;, we would appreciate it if you went to one of these sites and rated it. If you still can not find a package, follow the installation procedure on how to compile &krusader; from source. This very thorough HowTo describes the process in such detail that even newcomers should not have any problems. A new version scheme has been used since &krusader;-1.60.0 First digit - the major version Second digit(s) - percentage of features completed for this major version Third digit(s) - bugfixes. In essence, releasing &krusader;-1.60.0 means that we believe that &krusader; is about 60% done with all the features we had scheduled for the 1.x.x series. Series 2.x.x will be &kde; 4.x releases. Hopefully, it is easy to understand. krusader-x.xx.tar.gz &krusader; is released under the &gpl-lnk;. This means that THE PROGRAM IS PROVIDED "AS IS" WITH NO WARRANTY OF ANY KIND, even when it is marked as a stable release. krusader-x.xx-betax.tar.gz Before every stable release we release at least one development version in order to hunt down the bugs. These releases are beta releases and will probably contain some bugs. &dev-cvs-note; The beta release has 3 goals: Apply a feature-freeze until the stable is released, only bugs will be fixed. New features have to wait until the stable is released. Obtain feedback from &krusader; users so that we can fix the bugs. Give translators time to update the translations for the coming stable. Please read the &i18n-page-url;. krusader-cvs-yyyymmdd.tar.gz These builds are untested and come without any warranty. They may contain bugfixes, new features, or even new bugs. We provide daily snapshots of &krusader;'s CVS version. For those who are interested, the nightly tarball can be found on the &krucutedge-url;. Depending on the stage of development, this version will either be stable or unstable. Just before a stable release, the CVS version is almost stable. After a stable release new features will be committed into CVS, which might lead to the appearance of bugs. In some rare cases, the build will not even compile if we make a mistake. In that case we try to fix the error as soon as possible. &krusader; provides 2 nightly snapshots: krusader-cvs-yyyymmdd.tar.gz: make -f Makefile.cvs must be run before the ./configure script is available. krusader-cvs2-yyyymmdd.tar.gz: for users who have problems with the make -f Makefile.cvs command, we have already done this for you and the ./configure script is included in the tarball. This tarball is a bit bigger than the first one. check out from CVS. &krusader; can be checked out through anonymous (pserver) CVS with the following instruction set. The module you wish to check out must be specified as the module name. When prompted for a password for anonymous, press the &Enter; key. Currently, there are two module options: krusader_kde2: the &kde;2 branch, stable but it is basically v1.01 and there are no planned changes krusader_trinity: the &kde;3 branch that we currently use To check out &krusader; from CVS: $ cvs -d:pserver:anonymous@krusader.cvs.sourceforge.net:/cvsroot/krusader login $ cvs -z3 -d:pserver:anonymous@krusader.cvs.sourceforge.net:/cvsroot/krusader co krusader_trinity (note: updates from within the modules directory do not need the -d parameter) If you want to check out a specific version of &krusader; from CVS (⪚ &krusader;-1.60.0) : $ cvs -z3 -d:pserver:anonymous@krusader.cvs.sourceforge.net:/cvsroot/krusader co -rversion_1_60_0 krusader_trinity If you want to check out a specific date of &krusader; from CVS (⪚ &krusader;-2006-10-29) : $ cvs -z3 -d:pserver:anonymous@krusader.cvs.sourceforge.net:/cvsroot/krusader co -D2006-10-29 krusader_trinity Mostly being &gentoo; users, we provide a &gentoo-life-ebuild-url; for all those who want to stay on the bleeding edge of file management and do not want to miss the advantages of portage. Please take a look at our &krucutedge-url; for more installation details. We also provide &viewcvs-url; to browse the CVS repository. &subversion-url; is used for the &krusader; 2.x series for &kde;4. it is also possible to &browse-svn-repo-url;. To check out the latest &krusader; 1.x for &kde; 3 from SVN: (NOTE: at moment of writing use CVS for krusader_trinity, since krusader_trinity is developed in CVS and NOT in SVN, currently you will get an old version in SVN) $ svn co https://krusader.svn.sourceforge.net/svnroot/krusader/trunk/krusader_trinity To check out the latest &krusader; 2.x for &kde; 4 from SVN: $ svn co https://krusader.svn.sourceforge.net/svnroot/krusader/trunk/krusader_kde4 If you are looking for older releases we recommend the &sfmirrors-url;, available from our project page. Check the environment variables &kdeqtdir-lnk;. To compile and install &krusader; on your system, type the following in the base directory of the &krusader; package: $ ./configure $ make $ su -c 'make install' &krusaderui-rc-text; Since &krusader; uses autoconf and automake you should have no trouble compiling it. If you run into problems, read the detailed installation instructions below. These instructions should work as well on &debian; based distributions like: &ubuntu;, &kubuntu;, &linspire;, &kanotix;, ... Add the next lines in the ~/.bashrc configuration file export QTDIR=/usr export KDEDIR=/usr export export KDEDIRS=/opt/krusader:/usr Install the build dependencies for &krusader; # apt-get build-dep krusader Download the &krusader; sourcecode, unpack and enter the krusader_trinity directory. The next command will create ./configure $ make -f Makefile.cvs NOTE: you might need to upgrade automake and/or autoconf, if an error message appears. Install &krusader; in the /opt directory to not overwrite the official &debian; binary /usr/bin/krusader, so that krusader will run the official &debian; package and /opt/bin/krusader runs the compiled version. It's recommended to use enable the full debug, so that you can possible problems at us. Run configure. $ ./configure --prefix=/opt/krusader --enable-debug=full Compile &krusader; $ make Install Krusader $ su -c "make install" /opt/bin/krusader runs the compiled &krusader; version. Install the build dependencies for &krusader; Download the &krusader; sourcecode, unpack and enter the krusader_trinity directory. Now you can compile and install &krusader; $ make -f Makefile.cvs $ ./configure --prefix=/opt/krusader --enable-debug=full $ make $ su -c "make install" Ofcource it's impossible to cover all Linuxes, but here are the general installation instructions. Usually ./configure --prefix=/usr should be used, though options like /opt/krusader are usually better so that you don't overwrite files that are installed by your package managment system. Please don't use the /usr/local directory as it simply won't work. Install the build dependencies for &krusader; Download the &krusader; sourcecode, unpack and enter the krusader_trinity directory. Now you can compile and install &krusader; $ make -f Makefile.cvs $ ./configure --prefix=/usr $ make $ su -c "make install" The next section will explain how to install &krusader; step by step. Questions about the installation process have been asked many times and especially users new to &Linux; often have problems compiling software from source. Therefore, we are trying to keep the explanations as detailed as possible even if they are mostly not &krusader; specific. Experienced users may easily skip most of the steps. Unfortunately, because not all &Linux; distributions follow the &fhs-url; it is impossible to write a tutorial that would cover all circumstances. However, these guidelines will help you in the right direction. If you encountered problems, please read first this installation procedure and the &faq-lnk;. If the problem persists, use the &help-request-lnk; to ask for help. Install all packages and libraries that are needed for the compilation, please read the &faq-lnk;. If you install &kdevelop;, (almost) everything that you need to compile &krusader; will be installed on your computer. However, if you are not a developer, please follow the instructions and do not use &kdevelop; to compile &krusader;. Open your favourite terminal emulator (⪚ &konsole;). We recommend you create a separate directory to keep all the sources you compile in. This way you will have a better overview of the installed programs and it will be easier to uninstall them later. $ mkdir ~/source The chosen directory is just an example, any other will work. Copy the sources to the ~/source directory and unpack them. $ cp /"your_dir" /krusader-x.xx.tar.gz ~/source $ cd ~/source $ tar -xzvf krusader-x.xx.tar.gz Optional step: if you wish you can delete the tarball at this point as it is no longer needed. $ rm krusader-x.xx.tar.gz Change to the directory containing the sources. $ cd krusader-x.xx Check the environment variables QTDIRand KDEDIR. &krusader;'s ./configure script needs to know where the &Qt; and &kde; directories are. QTDIR: <path to your Qt installation> ⪚ /usr/lib/qt3 or /usr/qt3 KDEDIR: <path to your KDE installation> ⪚ /usr or /opt/trinity Normally your distribution will set them for you, but experience has shown that some do not. You can easily check the values with the echo command. $ echo $QTDIR/usr/lib/qt3 $ echo $KDEDIR/usr If both commands give an output, the enviroment variables are set (the above example are the settings of &mandriva;-&Linux;). In case you receive empty lines, the variables are not set and you have to set them manually. If you do not know what to set the variables to, or if you want to check if the variables are correctly set, ask your distributor or use the find command. $ find /usr /opt -name qtconfig -type f 2>/dev/null /usr/lib/qt3/bin/qtconfig $ find /usr /opt -name kdeinit -type f 2>/dev/null /usr/bin/kdeinit In this case /usr/lib/qt3 is your QTDIR and /usr is your KDEDIR. The installed binaries will go to /usr/bin. Now we will set the enviroment variables with the export command. $ export QTDIR=<replace with your QTDIR> $ export KDEDIR=<replace with your KDEDIR> These enviroment variables are only set for the lifetime of your current shell. When you close your terminal and open a new one they will be gone. Assuming &krusader; is not the only &Qt;/&kde; program you want to compile, we recommend to make these settings permanent (⪚ append both export commands to your /etc/profile) file. If you can notdetermine your KDEDIR, kde-config --prefix might help you. If you have downloaded a stable version "krusader-x.xx.tar.gz" or a beta version "krusader-x.xx-betax.tar.gz", you can skip this step. In this case the ./configure script is provided. If you have downloaded a CVS build or nightly tarball "krusader-cvs-yyyy-mm-dd.tar.gz"", you will have to run the following command to create the ./configure script: $ make -fMakefile.cvs If everything is OK you will see the following output on your screen: $ make -f Makefile.cvs This Makefile is only for the CVS repository This will be deleted before making the distribution *** Creating acinclude.m4 *** Creating list of subdirectories *** Creating configure.in *** Creating aclocal.m4 *** Creating configure *** Creating config.h template *** Creating Makefile templates *** Postprocessing Makefile templates *** Creating date/time stamp *** Finished Don't forget to run ./configure If you haven't done so in a while, run ./configure --help $ You will need to have autoconf 2.52, 2.53 or 2.54 and automake 1.6 (or higher) to run the make -f Makefile.cvs command If you encounter problems with this command click here. &krusader; provides two nightly builds (snapshots) one with a ./configure script and one without. Your &Linux; distro &krusader; RPM or DEB package will normally install &krusader; in the KDEDIR/bin directory. According to the &fhs-url;, any user installed files go to the /usr/local directory. If you wish &krusader; to be installed in another directory, it can be determed with the prefix option. If you do not have root access, /home/YOUR_USERNAME/.kde is probably a good choice. foo Krusader Project: ----------------- Source code location: . C Compiler: gcc C Compiler flags: -ansi -W -Wall -pedantic -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2 -Wformat-security -Wmissing-format-attribute C++ Compiler: g++ prefix: /usr/local kde_libraries: /usr/include kde_includes: /usr/lib kde_locale: /usr/share/locale qt_libraries: /usr/lib/qt3/lib qt_includes: /usr/lib/qt3/include KDEDIR: /usr QTDIR: /usr/lib/qt3 Install path: /usr/local/bin krusader version: 1.80.0 krusader binary: /usr/local/bin/krusader (after 'make install') Thank you for using Krusader Good - your configure finished. Start make now bash$ This is the output for &Mandrake;-&Linux; 10, other distributions may give a different output. At the end of the ./configure script you will find a summary of the most important settings, ⪚ where the &krusader; binary will be installed (after the 'make install' command). This part will also display a warning if the environment variables &kdeqtdir-lnk; are empty. Since &krusader;-1.70.0 ./configure has two specific &krusader; options: ./configure --without-konqueror : build &krusader; without support &konqueror;'s servicemenus, default=with. This means that &konqueror;'s right-click menu entries will not be available. ./configure --without-javascript : build &krusader; without JavaScript support, default=with. This means that the &javascript-console-lnk; will not be available. ./configure --without-acl : build &krusader; without ACL support default=with. Sometimes this option is needed if you get a ACL compile error when running make. In the past the support was always compiled in when the headers where found, now you have the choice. Use ./configure --help to see more options or read the INSTALL file in the &krusader; sources. If you used another --prefix= than $KDEDIR or /usr/local, it is recommended to do an extra check: $ kde-config --path exe /home/frank/.kde/bin/:/usr/bin/:/usr/local/bin/ $ If the <prefix_dir/bin> directory is not shown, you need to use e.g. export KDEDIRS=/usr/local:/usr. To make these settings permanent you can ⪚ append this export command to your /etc/profile file. After that you need to restart &kde;. If ./configure fails, take a look at &missing-libs-lnk;. Start the compilation process with the make command. $ make This will take about 3 - 40 minutes depending on how fast your computer runs. If everything goes well, it will ⪚ end with the following messages: foo make[2]: Leaving directory `/home/source/krusader_trinity/tar' make[2]: Entering directory `/home/source/krusader_trinity' make[2]: Leaving directory `/home/source/krusader_trinity' make[1]: Leaving directory `/home/source/krusader_trinity' bash$ If ./configure was successful and make failed for some reason, continue to read this page. If you can not find a solution to your problem, feel free to post a help request at our &forum-lnk;. If everything is correct, you can now install &krusader;. $ su -c 'make install' You will be asked to enter your root password. &krusaderui-rc-text; Now you can start &krusader;. Optional step: Cleaning up to save disk space. Note: All compiled files created with the makecommand will be deleted. $ make clean If you ever want to uninstall &krusader;, use $ su -c 'make uninstall' You will be asked to enter your root password. If you followed the installation procedure and still encountered problems installing &krusader;, refer to &faq-lnk;. If the problem persists, use the &help-request-lnk; to ask for help. &MacOS;-X port Since June 2006 &krusader; is added into the &krusader; finkproject.org repository Please check this url for the latest information about the &MacOS;-X port, please read the &fink-url; documentation for more information, all information below could be outdated, though they should still work :) From now on the port is maintained by Catalin Hritcu. Krusader is ported to &MacOS; thanks the &fink-url;-project and Jonas Bähr and &bodo-tasche-url; . Unfortunately the only *stable* kdelib-binaries which &fink-url; has to offer is currenly 3.1.4 which means you need to use &krusader;-1.40 . Unfortunately the &MacOS; X &krusader; port does not have the same power as in a native &Linux;-&kde; environment. To run &krusader; you need also X11, which doesn't interact with the rest of the &MacOS; desktop. We hope that &Qt;4/&kde;4 will solve most of these problems. If you want a more recent Krusader version you need to compile &kde;. With &fink-url; it is rather easy but it takes some CPU cycles. Installation Instructions for &krusader;-1.40 Download and install &fink-url; with the &kde;3.1 binaries provided by fink and read the documentation. Extract the krusader-1.40.fink.darwin-ppc.tar.bz2 package to /sw/fink/dist/local/main/ Only root can write here. You may have to create 'local' and 'main'. Run as root: fink install krusader Follow these instructions if you wish to compile more source code or use a more recent version of &krusader;: Install &apple-x11-url; Install the &apple-x11-sdk-url; developer-tools with X11 headers (gcc is included) Install the fink-base Compile kdelibs 3.4.1 or higher (fink provides the necessary .info files) Compile the &krusader;-tarball or follow steps 2 and 3 of the previous section if a recent &krusader;-package ⪚ krusader-1.70.0.fink.darwin-ppc.tar.bz2 is available Follow these instructions if you wish to compile &krusader;-1.80.0 : Install &apple-x11-url; nstall fink and enable fink unstable. Compile and install the &kde; bundle in fink: fink install bundle-kde-ssl (if you get “no package found” the previous step did not succeed). Use krusader.info (provided in the &krusader;-sourcecode) and then copy to /sw/fink/dists/local/main/finkinfo . Compile and install &krusader; in fink: fink install krusader Start X11 (startx) and in xterm run &krusader; Thanks to Catalin Hritcu for these install instructions. Type krusader (lower case) at a command prompt. You can create shortcut on your desktop or create an entry in the (&kde;) menu. Read the previous page and the &faq-lnk; if &krusader; doesn't start. When &krusader; is started from the command line, various options can be specified to modify its behavior. $ krusader WARNING: Mt.Man: Born, looking around to get familiar. foo Do not worry about the messages you get in the &konsole;. These messages are log messages that can be used for debugging &krusader;. You can also use &Alt; F2 to open the Run Command dialog box, type krusader (lower case) and press &Enter; or click on the Run button. If &krusader; is installed by an RPM or DEB package then usually &krusader; can be started from the &kmenu;. ⪚ on &Mandrake;-&Linux; 10.0 click on the &kicon; button and choose Applications File tools &krusader; . --left <path> start left panel at <path> --right <path> start right panel at <path> --left <path1>,<path2>,<path3> start left panel at <path1>,<path2>,<path3>, with tabs. --profile <panel-profile> load a panel-profile on startup (this overrides the default startup profile). Examples: $ krusader --left=<path> --right=<path> $ krusader --left=/mnt/cdrom --right=ftp://downloads@myserver.net $ krusader --left=<path1>,<path2> --right=<path1>,<path2>,<path3> $ krusader--profile <panel-profile> $ krusader --profile ftp-managment The standard &Qt; and &kde; command-line options are available, and can be listed by entering krusader --help . --help-qt List Qt-specific options --help-kde List KDE-specific options --help-all List all options --author Show the authors names -v,--version Show the version number --license Show license information When you run &krusader; for the first time, the &krusader; configuration module Konfigurator will show up and allow you to configure &krusader; as well as detect installed packers and tools. You can always run Konfigurator again from the &settingsmenu-lnk;. To make &krusader; the default file manager in Gnome, click here for more information. To make &krusader; the default file manager in &kde;, click here for more information. From version &krusader;-2.0.0 and higher is &kde;-4 only. At moment of writing &krusader;-2.0.0 is still under development, though it works :) "krusader_kde4.tar.gz" is the supposed name of the krusader tarball (it will be probably a different one ;) You can download the latest available krusader-2.x from SVN. DCMAKE_INSTALL_PREFIX is the location of the KDE DQT_INCLUDES $ tar -xzvf krusader_kde4.tar.gz $ cd krusader_kde4 $ cmake -DCMAKE_INSTALL_PREFIX=/usr/ -DQT_INCLUDES=/usr/share/qt4/include $ make $ su -c "make install"