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 not all features will 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.0: prefers &kde; >= 3.4 (otherwise not all features will be available) &krusader; v2.xx.x: &kde; 4 - &Qt; 4 The big challenge, maybe a first release in 2006 ;) 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 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 addons can be found on the &krudownload_url;. For more requirements, continue to read this chapter and read also the &faq_lnk; section. The latest information about &krusader; can be found on the &kruwebsite_url; . It's recommend 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, thanks! The latest version (and 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 third-parties and &krusader; users. Distributions who provide &krusader;: &suse_download_url; >= 9.3, Note: please use &krusader;-1.60.0 and not &krusader;-1.51 (might be instable 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 "unofficial bleeding-edge" DEB packages. Note: usually &debian; packages work also on distributions who are "based on &debian;", some of these provide their own (incompatible) packages. &ubuntu_kubuntu_download_url;, &linspire_download_url;, &knoppix; 4.x DVD, &kanotix;, ... &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 that your distro uses to install the &krusader; package, sometimes an internet connection is needed if &krusader; is not available on the &CD; or DVD. There are probably more distributions out there who include &krusader;, sorry we can't mention you all, though feedback is always welcome to improve this distrolist. Others &slackware; tgz binaries can usually found on the &krudownload_url;, or use &portpkg_url; that contains a &kru_slackbuild_url;, # portpkg krusader will do the job. There is a &macosx_download_url; port with the help of &fink_url; , the port is maintained by &bodo_tasche_url; . 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't find a package for your distribution, we recommend searching for it with &rpmfind_url; , &rpmpbone_url; or &rpmseek_url; . If you like &krusader; go to one of these sites and rate &krusader;, thanks. If you still can't find a package, please don't worry. We provide a very detailed installation procedure. This very thorough HowTo shows even newcomers how to compile &krusader; from source, even if you've never compiled a program from source. Please continue to read this chapter ;) We use a new version scheme 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. So in essence, releasing &krusader;-1.60.0, means that we believe that &krusader; is about 60% done with all the features we'd schedule for the 1.x.x series. Series 2.x.x will be &kde; 4.x releases. We hope it'd be 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, so that we can 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 the 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 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 even not compile if we make a mistake, in that case we try to fix the mistake 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 then the first one). Checkout 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 modulename. When prompted for a password for anonymous, simply press the &Enter; key. Currently, there are two module options: krusader_kde2: the &kde;2 branch, stable but it's basically v1.01 and there are no planned changes krusader_trinity: the &kde;3 branch, that we currently use To checkout &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 checkout a specific version of &krusader; from CVS (⪚ &krusader;-1.60.0) : $ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader co -rversion_1_60_0 krusader_trinity If you want to checkout a specific date of &krusader; from CVS (⪚ &krusader;-2005-05-23) : $ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader co -D2005-05-23 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 filemanagement and don't 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; will probably used for the &krusader; 2.x series for &kde;4. It's also possible to &browse_svn_repo_url;. To checkout the latest &krusader; 1.x for &kde; 3 from SVN: (NOTE: at moment of writing it's recommend to use CVS for krusader_trinity, since krusader_trinity is developed in CVS and not in SVN) $ svn co https://svn.sourceforge.net/svnroot/krusader/trunk/krusader_trinity To checkout the latest &krusader; 2.x for &kde; 4 from SVN: (NOTE: not yet available at moment of writing) $ svn co https://svn.sourceforge.net/svnroot/krusader/trunk/krusader_kde4 Looking for older releases? Try the &sfmirrors_url; available from our project page. Check the environment variables &kdeqtdir_lnk;. In order 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. Should you run into problems please read the detailed installation instructions below. The next section will explain step by step, in detail, how to install &krusader;. This question has 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. Because not all &Linux; distributions do follow the &fhs_url; it's unfortunately impossible to write a tutorial that always works in all circumstances, but with these guidelines will be a big help in the right direction. If you encounter problems, please read first this installation procedure and the &faq_lnk;, if this does not solve your problem then feel free to ask for help with an &help_request_lnk;. Install all needed packages and libraries that you need for the compilation, please read the &faq_lnk;. If you install &tdevelop; then (almost) everything that you need to compile &krusader; will be installed on your computer, BUT please don't use &tdevelop; to compile &krusader; if you are not a developer (possible automake hell), just follow the next instructions. Open your favourite terminal emulator (⪚ &konsole;). We recommend you create a separate directory to keep all the sources you compile in. This will give you a better overview of installed programs and makes it 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: the tarball is no longer needed at this point, you can delete it if you want or you can keep it if you like. $ rm krusader-x.xx.tar.gz Change to the directory containing the sources. $ cd krusader-x.xx Check the environment variables QTDIR and TDEDIR. &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 TDEDIR : <path to your KDE installation> ⪚ /usr or /opt/trinity Normally your distribution will set them for you, but experience has shown that some don't. You can easily check the values with the echo command. $ echo $QTDIR /usr/lib/qt3 $ echo $TDEDIR /usr If both commands give an output, the enviroment variables are set (the above example are the settings of &mandriva;-&Linux;). In case you just receive empty lines, the variables are not set and you have to set them it manually. If you have no idea 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 tdeinit -type f 2>/dev/null /usr/bin/tdeinit In this case /usr/lib/qt3 is your QTDIR and /usr is your TDEDIR. 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 TDEDIR=<replace with your TDEDIR> 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't determine your TDEDIR than tde-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 -f Makefile.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 2 nightly builds (snapshots) one with a ./configure script and one without. Your &Linux; distro &krusader; RPM or DEB package will usually install &krusader; in the TDEDIR/bin directory. According to the &fhs_url;, any user installed files should go to the /usr/local directory, but in some cases you might want that &krusader; will be installed in an other directory, this behaviour can be determed with the prefix option. If you don't have root access /home/YOUR_USERNAME/.kde is probably a good choice. $ ./configure --prefix=/usr/local This will take about 1 minute, if everything goes well it will ⪚ end with the following messages: 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 TDEDIR: /usr QTDIR: /usr/lib/qt3 Install path: /usr/local/bin krusader version: 1.51 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. 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 dit use the an other --prefix= than $TDEDIR or /usr/local , then it can't hurt to do an extra check: $ tde-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 TDEDIRS=/usr/local:/usr. To make these settings permanent you can ⪚ append this export command to your /etc/profile file. Than you need to restart &kde;, and check again. If ./configure fails, take a look at &missing_libs_lnk;. Start the compilation process with the make command. $ make This will take about 10 to 40 minutes, 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't find any solution for your problem then feel free to post a help request at our &forum_lnk;. If nothing went wrong, 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: if you want you can clean up to save some diskspace. Note: in this case all the compiled files created with the make command will be deleted. $ make clean If you ever want to uninstall &krusader;, just use $ su -c 'make uninstall' You will be asked to enter your root password. If you encounter problems with installing &krusader; please read first the &faq_lnk;. If this installation procedure and the FAQ does not solve the problem, feel free to ask for help with an &help_request_lnk;. Krusader is ported to &MacOS; thanks to 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 doesn't have the same power as in a native &Linux;-&kde; environement. To run &krusader; you need also X11 which doesn't realy interact with the rest of the &MacOS; desktop (drag and drop, etc...) We hope that &Qt;4/&kde;4 will solve most of these problems. When you want a higher Krusader version than you need to compile &kde; , what is not so difficult with &fink_url; 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 If you like to compile more sourcecode or if you want to use a more recent &krusader; version then these are the installation instructions. install &apple_x11_url; install the &apple_x11_sdk_url; developer-tools with X11 headers (gcc is included) install the fink-base compile tdelibs 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.60.0.fink.darwin-ppc.tar.bz2 is available 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 Don't 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 &ticon; button and choose ApplicationsFile 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;.