>&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 <link linkend="konfig-dependencies"
>here</link
>.</para>
<para
>A package of popular (un)packers, &krusader; itself and addons can be found on the &krudownload_url;.</para>
<para
>For more requirements, continue to read this chapter and read also the &faq_lnk; section.</para>
</sect1>
<sect1 id = "getting-krusader">
<title
>How to obtain &krusader;</title>
<para
>The latest information about &krusader; can be found on the &kruwebsite_url; .</para>
<sect2 id="krusader_download">
<title
>Download &krusader;</title>
<para
>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!</para>
<para
>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.</para>
<para
>Distributions who provide &krusader;: <itemizedlist
> <listitem
> <para
>&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)</para
> </listitem
> <listitem
> <para
>&fedora; via &fedora_extras_url; <command
># yum install krusader</command
> 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; .</para
> </listitem
> <listitem
> <para
>&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;, ...</para
> </listitem
> <listitem
> <para
>&mandriva_download_url; via the contrib repository <command
># urpmi krusader</command
> will do the job, &gentoo_download_url;, &yoper_download_url;</para
>Even more distributions can be found with &distrowatch_com_url;</para
> </listitem
> </itemizedlist
> 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. </para>
<para
>Others <itemizedlist>
<listitem>
<para
>&slackware; tgz binaries can usually found on the &krudownload_url;, or use &portpkg_url; that contains a &kru_slackbuild_url;, <command
># portpkg krusader</command
> will do the job.</para>
</listitem>
<listitem>
<para
>There is a &macosx_download_url; port with the help of &fink_url; , the port is maintained by &bodo_tasche_url; .</para>
</listitem>
</itemizedlist>
</para>
<para
>Installation via the &klik_protocol_url; . <itemizedlist>
<listitem>
<para
>&klik_krusader_url; downloads &krusader; provided by &debian; stable, more information is &klik_available_url; .</para>
</listitem>
<listitem>
<para
>&klik_krusader_latest_url; downloads the latest &klik_stable_krusader_url; provided by the &krusader; Krew.</para>
</listitem>
<listitem>
<para
>&klik_krusader_cvs_url; downloads a &klik_cvs_krusader_url; provided by the &krusader; Krew.</para>
</listitem>
</itemizedlist>
</para>
<para
>Search engines <itemizedlist
> <listitem
> <para
>You can also find packages on &Linux; software archives such as &freshmeat_url; or &kde_apps_url; .</para
> </listitem
> <listitem
> <para
>If you can't find a package for your distribution, we recommend searching for it with &rpmfind_url; , &rpmpbone_url; or &rpmseek_url; .</para
> </listitem
> </itemizedlist
> If you like &krusader; go to one of these sites and rate &krusader;, thanks. </para>
<para
>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 ;)</para>
</sect2>
<sect2 id="version_scheme">
<title
>Version scheme</title>
<para
>We use a new version scheme since &krusader;-1.60.0 <itemizedlist
> <listitem
><para
>First digit - the major version </para
></listitem
> <listitem
><para
>Second digit(s) - percentage of features completed for this major version </para
></listitem
> <listitem
><para
>third digit(s) - bugfixes. </para
></listitem
> </itemizedlist
> 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. </para>
</sect2>
<sect2 id="krusader_stable">
<title
>Stable version</title>
<para
><filename
>krusader-x.xx.tar.gz</filename
></para>
<note
><para
>&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.</para
></note>
</sect2>
<sect2 id="krusader_devel">
<title
>Development version (beta release)</title>
<para
><filename
>krusader-x.xx-betax.tar.gz</filename
></para>
<para
>Before every stable release we release at least one development version, so that we can hunt down the bugs.</para>
<warning
><para
>These releases are beta releases and will probably contain some bugs.</para
></warning
> &dev_cvs_note; <para
>The beta release has 3 goals: <itemizedlist>
<listitem>
<para
>Apply a feature-freeze until the stable is released, only bugs will be fixed. New features have to wait until the stable is released.</para>
</listitem>
<listitem>
<para
>Obtain feedback from &krusader; users so that we can fix the bugs.</para>
</listitem>
<listitem>
<para
>Give translators the time to update the translations, for the coming stable. Please read the &i18n_page_url;</para>
</listitem>
</itemizedlist>
</para>
</sect2>
<sect2 id="krusader_cvs">
<title
>CVS builds</title>
<para
><filename
>krusader-cvs-yyyymmdd.tar.gz</filename
></para>
<warning
><para
>These builds are untested and come without any warranty. They may contain bugfixes, new features or new bugs!</para
></warning>
<para
>We provide daily snapshots of &krusader;'s CVS version. For those who are interested, the <emphasis role="bold"
>nightly tarball</emphasis
> 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.</para>
> command, we have already done this for you and the <command
>./configure</command
> script is included in the tarball (This tarball is a bit bigger then the first one). </para>
</listitem>
</orderedlist>
</para>
<para
><emphasis role="bold"
>Checkout from CVS</emphasis
>. &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.</para>
<para
>Currently, there are two module options: <itemizedlist>
<listitem
><para
>krusader_kde2: the &kde;2 branch, stable but it's basically v1.01 and there are no planned changes</para
>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.</para>
<para
>We also provide &viewcvs_url; to browse the CVS repository.</para>
</sect2>
<sect2 id="krusader_svn">
<title
>Subversion</title>
<para
>&subversion_url; will probably used for the &krusader; 2.x series for &kde;4. It's also possible to &browse_svn_repo_url;.</para>
>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) <screen
> you should have no trouble compiling it. Should you run into problems please read the detailed installation instructions below.</para>
</sect2>
<sect2 id="install_tutorial">
<title
>Installation Tutorial</title>
<para
>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.</para>
<para
>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.</para>
<note
><para
>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;. </para
></note>
<orderedlist>
<listitem>
<para
>Install all needed packages and libraries that you need for the compilation, please read the &faq_lnk;. <tip
>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.</para
>Open your favourite terminal emulator (⪚ &konsole;).</para>
<!-- Empty line to make it more readable -->
</listitem>
<listitem>
<para
>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. <screen
> 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 <command
>find</command
> command. <screen
><prompt>$</prompt> <userinput><command>find</command> <option>/usr /opt -name</option> qtconfig <option>-type f 2>/dev/null</option></userinput>
>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 &TQt;/&tde; program you want to compile, we recommend to make these settings permanent (⪚ append both export commands to your <filename class="directory"
> directory. According to the &fhs_url;, any user installed files should go to the <filename
>/usr/local</filename
> 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 <filename
> 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 &kdetqtdir_lnk; are empty. </para
> has two specific &krusader; options: <itemizedlist
> <listitem
> <para
><userinput
><command
>./configure</command
> <option
>--without-konqueror</option
></userinput
>: build Krusader without support &konqueror;'s servicemenus, default=with. This means that &konqueror;'s right-click menu entries will not be available.</para
> </listitem
> <listitem
> <para
><userinput
><command
>./configure</command
> <option
>--without-javascript</option
></userinput
>: build Krusader without JavaScript support, default=with. This means that the &javascript_console_lnk; will not be available.</para
> </listitem
> </itemizedlist
> In the past the support was always compiled in when the headers where found, now you have the choice. </para>
<para
>Use <userinput
><command
>./configure</command
> <option
>--help</option
></userinput
> to see more options or read the <filename
>INSTALL</filename
> file in the &krusader; sources.</para>
<para
>If you dit use the an other --prefix= than <filename
> 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;.</para>
<!-- Empty line to make it more readable -->
</listitem>
<listitem>
<para
>If nothing went wrong, you can now install &krusader;. <screen
> You will be asked to enter your root password.</para>
<para
></para
> <!-- Empty line to make it more readable -->
</listitem>
</orderedlist>
<para
>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;.</para>
</sect2>
</sect1>
<sect1 id="mac-port">
<title
>&MacOS;-x port</title>
<para
>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. </para>
<para
>Installation Instructions for &krusader;-1.40 <orderedlist>
<listitem>
<para
>Download and install &fink_url; with the &kde;3.1 binaries provided by fink and read the documentation.</para>
</listitem>
<listitem>
<para
>Extract the <filename
>krusader-1.40.fink.darwin-ppc.tar.bz2</filename
> package to <filename
>/sw/fink/dist/local/main/</filename
> Only root can write here, you may have to create 'local' and 'main' </para>
</listitem>
<listitem>
<para
>Run as root: <command
>fink install krusader</command
></para>
</listitem>
</orderedlist>
</para>
<para
>If you like to compile more sourcecode or if you want to use a more recent &krusader; version then these are the installation instructions. <orderedlist>
<listitem>
<para
>install &apple_x11_url;</para>
</listitem>
<listitem>
<para
>install the &apple_x11_sdk_url; developer-tools with X11 headers (gcc is included)</para>
> (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.</para>
<para
>When &krusader; is started from the command-line, various options can be specified to modify its behavior.</para>
>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 <emphasis role="bold"
>When you run &krusader; for the first time the &krusader; configuration module <link linkend="konfigurator"
>Konfigurator</link
> 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;.</para>
