1
<appendix id = "installation">
3
<!-- **********************************************************************
5
++++++++++++++++++++++++++
6
copyright : (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006
7
Rafi Yanai, Shie Erlich, Frank Schoolmeesters
9
e-mail : krusader@users.sourceforge.net
10
web site : http://www.krusader.org
11
description : a Krusader Documentation File
13
***************************************************************************
14
* Permission is granted to copy, distribute and/or modify this *
15
* document under the terms of the GNU Free Documentation License, *
16
* Version 1.1 or any later version published by the Free Software *
17
* Foundation; with no Invariant Sections, no Front-Cover Texts and *
18
* no Back-Cover Texts. A copy of the license is available on the *
19
* GNU site http://www.gnu.org/licenses/fdl.html or by writing to: *
20
* Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, *
21
* MA 02111-1307, USA. *
22
*********************************************************************** -->
27
<sect1 id="requirements">
32
>In order to successfully use the most recent &krusader;, you need &kde;libs >= 3.4</para>
35
>Required &kde; version: <itemizedlist>
38
>&krusader; v1.01: &kde; 2</para>
42
>&krusader; v1.02 - 1.40: &kde; 3.0 - &kde; 3.2</para>
46
>&krusader; 1.40: prefers &kde; 3.2 (otherwise not all features will be available)</para>
50
>&krusader; v1.50 - v1.51: &kde; 3.2 - &kde; 3.3 (Konfigurator crash on &kde; 3.4)</para>
54
>&krusader; v1.60.0 - v1.70.0: &kde; 3.3 - &kde; 3.5</para>
58
>&krusader; 1.70.0: prefers &kde; >= 3.4 (otherwise not all features will be available)</para>
62
>&krusader; v2.xx.x: &kde; 4 - &Qt; 4 The big challenge, maybe a first release in 2006 ;)</para>
68
>Platforms: <itemizedlist>
71
>All POSIX (&Linux;/BSD/&UNIX;-like OSes), &Solaris;.</para
75
>All BSD Platforms (&freebsd;/&netbsd;/&openbsd;/&MacOS;).</para
81
>&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"
86
>A package of popular (un)packers, &krusader; itself and addons can be found on the &krudownload_url;.</para>
89
>For more requirements, continue to read this chapter and read also the &faq_lnk; section.</para>
94
<sect1 id = "getting-krusader">
96
>How to obtain &krusader;</title>
99
>The latest information about &krusader; can be found on the &kruwebsite_url; .</para>
101
<sect2 id="krusader_download">
103
>Download &krusader;</title>
106
>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>
109
>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>
112
>Distributions who provide &krusader;: <itemizedlist
116
>= 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
120
>&fedora; via &fedora_extras_url; <command
121
># yum install krusader</command
122
> 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
126
>&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
130
>&mandriva_download_url; via the contrib repository <command
131
># urpmi krusader</command
132
> will do the job, &gentoo_download_url;, &yoper_download_url;</para
136
>&archlinux_download_url;, &frugalware_linux_download_url;, &pclinuxos_download_url;, &altlinux_download_url;</para
140
>&freebsd_download_url;, the port is maintained by <link linkend="credits"
141
>Heiner Eichmann</link
146
>&netbsd_download_url;, &lunarlinux_download_url; ,&arklinux;, &openlx;, &sourcemage;.</para
150
>Even more distributions can be found with &distrowatch_com_url;</para
153
> 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>
156
>Others <itemizedlist>
159
>&slackware; tgz binaries can usually found on the &krudownload_url;, or use &portpkg_url; that contains a &kru_slackbuild_url;, <command
160
># portpkg krusader</command
161
> will do the job.</para>
165
>There is a &macosx_download_url; port with the help of &fink_url; , the port is maintained by &bodo_tasche_url; .</para>
171
>Installation via the &klik_protocol_url; . <itemizedlist>
174
>&klik_krusader_url; downloads &krusader; provided by &debian; stable, more information is &klik_available_url; .</para>
178
>&klik_krusader_latest_url; downloads the latest &klik_stable_krusader_url; provided by the &krusader; Krew.</para>
182
>&klik_krusader_cvs_url; downloads a &klik_cvs_krusader_url; provided by the &krusader; Krew.</para>
191
>Search engines <itemizedlist
194
>You can also find packages on &Linux; software archives such as &freshmeat_url; or &kde_apps_url; .</para
198
>If you can't find a package for your distribution, we recommend searching for it with &rpmfind_url; , &rpmpbone_url; or &rpmseek_url; .</para
201
> If you like &krusader; go to one of these sites and rate &krusader;, thanks. </para>
205
>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>
209
<sect2 id="version_scheme">
211
>Version scheme</title>
213
>We use a new version scheme since &krusader;-1.60.0 <itemizedlist
216
>First digit - the major version </para
220
>Second digit(s) - percentage of features completed for this major version </para
224
>third digit(s) - bugfixes. </para
227
> 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>
230
<sect2 id="krusader_stable">
232
>Stable version</title>
235
>krusader-x.xx.tar.gz</filename
239
>&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
244
<sect2 id="krusader_devel">
246
>Development version (beta release)</title>
249
>krusader-x.xx-betax.tar.gz</filename
252
>Before every stable release we release at least one development version, so that we can hunt down the bugs.</para>
256
>These releases are beta releases and will probably contain some bugs.</para
258
> &dev_cvs_note; <para
259
>The beta release has 3 goals: <itemizedlist>
262
>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>
266
>Obtain feedback from &krusader; users so that we can fix the bugs.</para>
270
>Give translators the time to update the translations, for the coming stable. Please read the &i18n_page_url;</para>
278
<sect2 id="krusader_cvs">
283
>krusader-cvs-yyyymmdd.tar.gz</filename
288
>These builds are untested and come without any warranty. They may contain bugfixes, new features or new bugs!</para
292
>We provide daily snapshots of &krusader;'s CVS version. For those who are interested, the <emphasis role="bold"
293
>nightly tarball</emphasis
294
> 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>
297
>&krusader; provides 2 nightly snapshots: <orderedlist numeration="arabic">
301
>krusader-cvs-yyyymmdd.tar.gz</filename
303
>make -f Makefile.cvs</command
304
> must be run before the <command
305
>./configure</command
306
> script is available</para>
311
>krusader-cvs2-yyyymmdd.tar.gz</filename
312
>: for users who have problems with the <command
313
>make -f Makefile.cvs</command
314
> command, we have already done this for you and the <command
315
>./configure</command
316
> script is included in the tarball (This tarball is a bit bigger then the first one). </para>
322
><emphasis role="bold"
323
>Checkout from CVS</emphasis
324
>. &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>
326
>Currently, there are two module options: <itemizedlist>
329
>krusader_kde2: the &kde;2 branch, stable but it's basically v1.01 and there are no planned changes</para
333
>krusader_kde3: the &kde;3 branch, that we currently use</para
339
>To checkout &krusader; from CVS: <screen
340
><prompt>$</prompt> <userinput><command>cvs</command> <option>-d:pserver:anonymous@krusader.cvs.sourceforge.net:/cvsroot/krusader login</option></userinput></screen
342
><prompt>$</prompt> <userinput><command>cvs</command> <option>-z3 -d:pserver:anonymous@krusader.cvs.sourceforge.net:/cvsroot/krusader co krusader_kde3</option></userinput></screen
343
> (note: updates from within the modules directory do not need the -d parameter)</para>
346
>If you want to checkout a specific version of &krusader; from CVS (⪚ &krusader;-1.60.0) : <screen
347
><prompt>$</prompt> <userinput><command>cvs</command> <option>-z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader co -rversion_1_60_0 krusader_kde3</option></userinput></screen>
351
>If you want to checkout a specific date of &krusader; from CVS (⪚ &krusader;-2005-05-23) : <screen
352
><prompt>$</prompt> <userinput><command>cvs</command> <option>-z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/krusader co -D2005-05-23 krusader_kde3</option></userinput></screen>
356
>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>
359
>We also provide &viewcvs_url; to browse the CVS repository.</para>
364
<sect2 id="krusader_svn">
368
>&subversion_url; will probably used for the &krusader; 2.x series for &kde;4. It's also possible to &browse_svn_repo_url;.</para>
371
>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_kde3, since krusader_kde3 is developed in CVS and not in SVN) <screen
372
><prompt>$</prompt> <userinput><command>svn</command> <option>co https://svn.sourceforge.net/svnroot/krusader/trunk/krusader_kde3</option></userinput></screen
373
> To checkout the latest &krusader; 2.x for &kde; 4 from SVN: (NOTE: not yet available at moment of writing) <screen
374
><prompt>$</prompt> <userinput><command>svn</command> <option>co https://svn.sourceforge.net/svnroot/krusader/trunk/krusader_kde4</option></userinput></screen>
379
<sect2 id="krusader_old">
381
>Older releases</title>
383
>Looking for older releases? Try the &sfmirrors_url; available from our project page.</para>
389
<sect1 id="compilation">
391
>Compilation and installation</title>
393
<sect2 id="sourcedownload">
395
>I have downloaded the sources for &krusader;. What now?</title>
398
>Check the environment variables &kdeqtdir_lnk;.</para>
401
>In order to compile and install &krusader; on your system, type the following in the base directory of the &krusader; package:</para>
404
><prompt>$</prompt> <userinput><command>./configure</command></userinput>
405
<prompt>$</prompt> <userinput><command>make</command></userinput>
406
<prompt>$</prompt> <userinput><command>su -c 'make</command> <option>install'</option></userinput></screen>
407
&krusaderui_rc_text; <para
408
>Since &krusader; uses <command
412
> you should have no trouble compiling it. Should you run into problems please read the detailed installation instructions below.</para>
417
<sect2 id="install_tutorial">
419
>Installation Tutorial</title>
422
>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>
425
>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>
429
>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
436
>Install all needed packages and libraries that you need for the compilation, please read the &faq_lnk;. <tip
438
>If you install &kdevelop; then (almost) everything that you need to compile &krusader; will be installed on your computer, BUT please don't use &kdevelop; to compile &krusader; if you are not a developer (possible automake hell), just follow the next instructions.</para
441
<!-- Empty line to make it more readable -->
446
>Open your favourite terminal emulator (⪚ &konsole;).</para>
447
<!-- Empty line to make it more readable -->
453
>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
454
><prompt>$</prompt> <userinput><command>mkdir</command> ~/source</userinput></screen
455
> The chosen directory is just an example, any other will work.</para>
456
<!-- Empty line to make it more readable -->
457
<!-- Empty line to make it more readable (second line is needed) -->
463
>Copy the sources to the <filename
465
> directory and unpack them. <screen
466
><prompt>$</prompt> <userinput><command>cp</command> /<replaceable>"your_dir"</replaceable>/krusader-x.xx.tar.gz ~/source</userinput></screen>
468
><prompt>$</prompt> <userinput><command>cd</command> ~/source</userinput></screen>
470
><prompt>$</prompt> <userinput><command>tar</command> <option>-xzvf</option> krusader-x.xx.tar.gz</userinput></screen
472
<!-- Empty line to make it more readable -->
478
>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. <screen
479
><prompt>$</prompt> <userinput><command>rm</command> krusader-x.xx.tar.gz</userinput></screen
481
<!-- Empty line to make it more readable -->
487
>Change to the directory containing the sources. <screen
488
><prompt>$</prompt> <userinput><command>cd</command> krusader-x.xx</userinput></screen
490
<!-- Empty line to make it more readable -->
494
<listitem id="kde_qt_dir">
496
>Check the environment variables <envar
500
>. &krusader;'s <command
501
>./configure</command
502
> script needs to know where the &Qt; and &kde; directories are. </para>
508
><path to your Qt installation></replaceable
510
>/usr/lib/qt3</filename
519
><path to your KDE installation></replaceable
527
>Normally your distribution will set them for you, but experience has shown that some don't. You can easily check the values with the <command
530
><prompt>$</prompt> <userinput><command>echo</command> $QTDIR</userinput>
532
<prompt>$</prompt> <userinput><command>echo</command> $KDEDIR</userinput>
534
> 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
537
><prompt>$</prompt> <userinput><command>find</command> <option>/usr /opt -name</option> qtconfig <option>-type f 2>/dev/null</option></userinput>
538
/usr/lib/qt3/bin/qtconfig
539
<prompt>$</prompt> <userinput><command>find</command> <option>/usr /opt -name</option> kdeinit <option>-type f 2>/dev/null</option></userinput>
540
/usr/bin/kdeinit</screen
541
> In this case <filename
542
>/usr/lib/qt3</filename
549
>. The installed binaries will go to <filename
551
>. Now we will set the enviroment variables with the <command
554
><prompt>$</prompt> <userinput><command>export</command> QTDIR=<replaceable><replace with your QTDIR></replaceable></userinput></screen>
556
><prompt>$</prompt> <userinput><command>export</command> KDEDIR=<replaceable><replace with your KDEDIR></replaceable></userinput></screen>
561
>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 <filename class="directory"
562
>/etc/profile</filename
567
>If you can't determine your KDEDIR than <command
568
>kde-config --prefix</command
569
> might help you.</para>
571
<!-- Empty line to make it more readable -->
572
<!-- Empty line to make it more readable (second line is needed) -->
580
>If you have downloaded a stable version <filename
581
>"krusader-x.xx.tar.gz"</filename
582
> or a beta version <filename
583
>"krusader-x.xx-betax.tar.gz"</filename
584
>, you can skip this step, in this case the <filename
585
>./configure</filename
586
> script is provided.</para>
589
>If you have downloaded a CVS build or nightly tarball <filename
590
>"krusader-cvs-yyyy-mm-dd.tar.gz"</filename
591
>", you will have to run the following command to create the <filename
592
>./configure</filename
594
><prompt>$</prompt> <userinput><command>make</command> <option>-f</option> Makefile.cvs</userinput></screen
598
>If everything is OK you will see the following output on your screen: <screen
599
><prompt>$</prompt> <userinput><command>make</command> <option>-f</option> Makefile.cvs</userinput>
600
This Makefile is only for the CVS repository
601
This will be deleted before making the distribution
602
*** Creating acinclude.m4
603
*** Creating list of subdirectories
604
*** Creating configure.in
605
*** Creating aclocal.m4
606
*** Creating configure
607
*** Creating config.h template
608
*** Creating Makefile templates
609
*** Postprocessing Makefile templates
610
*** Creating date/time stamp
612
Don't forget to run ./configure
613
If you haven't done so in a while, run ./configure --help
614
<prompt>$</prompt></screen>
619
>You will need to have: <application
620
>autoconf 2.52, 2.53 or 2.54</application
622
>automake 1.6</application
623
> (or higher) to run the <command
624
>make -f Makefile.cvs</command
630
>If you encounter problems with this command click <link linkend="krusader_cvs"
632
>. &krusader; provides 2 nightly builds (snapshots) one with a <filename
633
>./configure</filename
634
> script and one without.</para
637
<!-- Empty line to make it more readable -->
638
<!-- Empty line to make it more readable (second line is needed) -->
644
>Your &Linux; distro &krusader; RPM or DEB package will usually install &krusader; in the <filename
645
>KDEDIR/bin</filename
646
> directory. According to the &fhs_url;, any user installed files should go to the <filename
647
>/usr/local</filename
648
> 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
649
>/home/YOUR_USERNAME/.kde</filename
650
> is probably a good choice. <screen
651
><prompt>$</prompt> <userinput><command>./configure</command> <option>--prefix=/usr/local</option></userinput></screen
655
>This will take about 1 minute, if everything goes well it will ⪚ end with the following messages: </para>
664
Source code location: .
666
C Compiler flags: -ansi -W -Wall -pedantic -Wchar-subscripts -Wshadow -Wpointer-arith
667
-Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2
668
-Wformat-security -Wmissing-format-attribute
671
kde_libraries: /usr/include
672
kde_includes: /usr/lib
673
kde_locale: /usr/share/locale
674
qt_libraries: /usr/lib/qt3/lib
675
qt_includes: /usr/lib/qt3/include
678
Install path: /usr/local/bin
679
krusader version: 1.51
680
krusader binary: /usr/local/bin/krusader (after 'make install')
681
Thank you for using Krusader
683
Good - your configure finished. Start make now
684
<prompt>bash$</prompt>
689
>This is the output for &Mandrake;-&Linux; 10, other distributions may give a different output.</para>
693
>At the end of the <command
694
>./configure</command
695
> 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. </para
698
<!-- Empty line to make it more readable -->
701
>Since &krusader;-1.70.0 <command
702
>./configure</command
703
> has two specific &krusader; options: <itemizedlist
708
>./configure</command
710
>--without-konqueror</option
712
>: build Krusader without support &konqueror;'s servicemenus, default=with. This means that &konqueror;'s right-click menu entries will not be available.</para
718
>./configure</command
720
>--without-javascript</option
722
>: build Krusader without JavaScript support, default=with. This means that the &javascript_console_lnk; will not be available.</para
725
> In the past the support was always compiled in when the headers where found, now you have the choice. </para>
730
>./configure</command
734
> to see more options or read the <filename
736
> file in the &krusader; sources.</para>
739
>If you dit use the an other --prefix= than <filename
740
>$KDEDIR or /usr/local</filename
741
> , then it can't hurt to do an extra check: <screen
742
><prompt>$</prompt> <userinput><command>kde-config</command> <option>--path exe</option></userinput>
743
/home/frank/.kde/bin/:/usr/bin/:/usr/local/bin/
744
<prompt>$</prompt></screen
745
> If the <prefix_dir/bin> directory is not shown, you need to use e.g. <command
746
>export KDEDIRS=/usr/local:/usr</command
747
>. To make these settings permanent you can ⪚ append this export command to your <filename
748
>/etc/profile</filename
749
> file. Than you need to restart &kde;, and check again. </para>
755
>./configure</command
756
> fails, take a look at &missing_libs_lnk;.</para
759
<!-- Empty line to make it more readable -->
766
>Start the compilation process with the <command
769
><prompt>$</prompt> <userinput><command>make</command></userinput></screen
770
> This will take about 10 to 40 minutes, if everything goes well it will ⪚ end with the following messages: <screen
772
make[2]: Leaving directory `/home/source/krusader_kde3/tar'
773
make[2]: Entering directory `/home/source/krusader_kde3'
774
make[2]: Leaving directory `/home/source/krusader_kde3'
775
make[1]: Leaving directory `/home/source/krusader_kde3'
776
<prompt>bash$</prompt>
780
<!-- Empty line to make it more readable -->
784
>./configure</command
785
> was successful and <command
787
> 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>
789
<!-- Empty line to make it more readable -->
795
>If nothing went wrong, you can now install &krusader;. <screen
796
><prompt>$</prompt> <userinput><command>su -c 'make</command> <option>install'</option></userinput></screen
797
> You will be asked to enter your root password.</para>
799
<!-- Empty line to make it more readable -->
800
<!-- Empty line to make it more readable (second line is needed) -->
805
>&krusaderui_rc_text; <para
807
> <!-- Empty line to make it more readable -->
812
>Now you can <link linkend="starting-krusader"
817
> <!-- Empty line to make it more readable -->
824
>Optional step: if you want you can clean up to save some diskspace. Note: in this case all the compiled files created with the <command
826
> command will be deleted. <screen
827
><prompt>$</prompt> <userinput><command>make</command> <option>clean</option></userinput></screen>
830
<!-- Empty line to make it more readable -->
831
<!-- Empty line to make it more readable (second line is needed) -->
837
>If you ever want to uninstall &krusader;, just use <screen
838
><prompt>$</prompt> <userinput><command>su -c 'make</command> <option>uninstall'</option></userinput></screen
839
> You will be asked to enter your root password.</para>
843
> <!-- Empty line to make it more readable -->
850
>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>
859
<sect1 id="mac-port">
861
>&MacOS;-x port</title>
864
>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>
868
>Installation Instructions for &krusader;-1.40 <orderedlist>
872
>Download and install &fink_url; with the &kde;3.1 binaries provided by fink and read the documentation.</para>
877
>Extract the <filename
878
>krusader-1.40.fink.darwin-ppc.tar.bz2</filename
879
> package to <filename
880
>/sw/fink/dist/local/main/</filename
881
> Only root can write here, you may have to create 'local' and 'main' </para>
886
>Run as root: <command
887
>fink install krusader</command
896
>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>
900
>install &apple_x11_url;</para>
905
>install the &apple_x11_sdk_url; developer-tools with X11 headers (gcc is included)</para>
910
>install the fink-base</para>
915
>compile kdelibs 3.4.1 or higher (fink provides the necessary <filename
922
>compile the &krusader;-tarball or follow steps 2 and 3 of the previous section if a recent &krusader;-package ⪚ <filename
923
>krusader-1.60.0.fink.darwin-ppc.tar.bz2</filename
924
> is available</para>
933
<sect1 id="starting-krusader">
935
>Starting &krusader;</title>
942
> (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>
945
>When &krusader; is started from the command-line, various options can be specified to modify its behavior.</para>
949
><prompt>$</prompt> <userinput><command>krusader</command></userinput>
950
WARNING: Mt.Man: Born, looking around to get familiar.
956
>Don't worry about the messages you get in the &konsole;. These messages are log messages that can be used for debugging &krusader;.</para
960
>You can also use <keycombo action="simul"
964
> to open the Run Command dialog box, type <userinput
968
> (lower case) and press &Enter; or click on the <guibutton
973
>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 <emphasis role="bold"
976
>Applications</guimenuitem
978
>File tools</guimenuitem
980
>&krusader;</guimenuitem
989
>Command-line options:</title>
995
><path></replaceable
1000
>start left panel at <path></action
1010
><path></replaceable
1015
>start right panel at <path></action
1025
><path1>,<path2>,<path3></replaceable
1030
>start left panel at <path1>,<path2>,<path3>, with tabs.</action
1040
><panel-profile></replaceable
1045
>load a <link linkend="panel_profiles"
1046
>panel-profile</link
1047
> on startup (this overrides the <link linkend="konfig-startup"
1048
>default startup profile</link
1059
><prompt>$</prompt> <userinput><command>krusader</command> <replaceable>--left=<path> --right=<path></replaceable></userinput></screen>
1061
><prompt>$</prompt> <userinput><command>krusader</command> <replaceable>--left=/mnt/cdrom --right=ftp://downloads@myserver.net</replaceable></userinput></screen>
1063
><prompt>$</prompt> <userinput><command>krusader</command> <replaceable>--left=<path1>,<path2> --right=<path1>,<path2>,<path3></replaceable></userinput></screen>
1065
><prompt>$</prompt> <userinput><command>krusader</command> <replaceable>--profile <panel-profile></replaceable></userinput></screen>
1067
><prompt>$</prompt> <userinput><command>krusader</command> <replaceable>--profile ftp-managment</replaceable></userinput></screen>
1071
>The standard &Qt; and &kde; command-line options are available, and can be listed by entering <userinput
1081
>Other command-line options:</title>
1090
>List Qt-specific options</action
1102
>List KDE-specific options</action
1114
>List all options</action
1126
>Show the authors names</action
1133
>-v,--version</option
1138
>Show the version number</action
1150
>Show license information</action
1158
<sect1 id="configuration">
1160
>Configure &krusader;</title>
1163
>When you run &krusader; for the first time the &krusader; configuration module <link linkend="konfigurator"
1165
> 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>
added
removed
doc/ru/installation.docbook
