Packete??? Bin neu!!

[basti12345]

Hi Allerseits!!

Ich hab so erst seit 3 Tagen Linux und mache Fortschritte auch, wenn ich überhaupt keinen Plan habe was ich eigentlich mache!!
Leider sind meine Fortschritte nicht die Größten, denn ich habe es noch kein einziges Mal geschafft, ein rpm Package zu installieren, nachdem irgendeine bedingte Abhängikeit nicht da war!!!
1. Denn erstens schaffe ich es nicht eine tar datei zu installieren, sollte dies der Fall sein. Denn dann gehts ja erstmal richtig los, und ich bin total überfordert, wenn ich dann in der Readme überhaupt nichts mehr checke!!
2. Wenn ich danach irgendwelche anderen rpm Packages installieren soll, dann brauchen die meistens wieder irgendwelche Anderen packages, die ich nicht habe usw. !! Deshalb meine Fragen!!
1. Wie macht ihr das??
2. Gibt es irgendwelche 5 Gb packete, in denen alle anderen Packete enthalten sind???
.... ich habe übrigends die Suse Linux 9.2 Version, die man im Internet runterladen kann (3.2 Gb) und habe alle Packete installiert, die ich installieren konnte!!!

Ach und! (wo werden eigentlich die ganzen dateien hinkopiert, wenn ich ein Rpm package installiere??
Also HILFE und Danke!!!

[BloodyBullet]

Normalerweise sollte er die Abhängigkeiten automatisch auflösen und dir entweder alle zu installierenden Pakete anzeigen bzw. automatisch mitinstallieren.

Ich gebe dir einen gut gemeinten Rat, setze dich intensiver mit Linux auseinander -> Dokumentationen lesen.

MfG

[DERRICHTER]

Du solltest dich schon entscheiden. RPM-Pakete können üblicherweise über yast oder kpackage, aber auch über eine shell (console) mit den entsprechenden Befehlen installiert werden. Für den Anfänger ist die Installation über yast oder kpackage die erste Wahl. Tar-Dateien werden über eine shell mit entsprechenden Befehlszeilen installiert, nachdem sie zuvor entpackt (archiver, ark) wurden. Es besteht bei rpm's auch die Möglichkeit, Pakete über apt-rpm zu suchen.

Abhängigkeiten: Wenn Du über yast von der yast-source-Quelle installierst oder es sich um Dateien handelt, die von der DVD (bei Dir ja wohl nicht der Fall) installiert werden, werden Abhängigkeiten automatisch aufgelöst. Kommen unter yast krypitsche Warnmeldungen mit diversen Warnzeichen (beliebt auch, dass folgenden 768 Pakete gelöscht werden sollen ...), dann sollte man einfach nachschauen, ob das fehlende Paket anderweitig findet (z. B. www.rpmseek.com ; http://packman.links2linux.de ; ftp://ftp.gwdg.de/linux/suse/apt/SuSE/9.2-i386). Wenn ja, dann wegen der Warnmeldung einfach auf ignorieren drücken (nachdem man sich das Paket, das noch benötigt wird, gemerkt hat) und dieses über yast nachinstallieren. Bei kpackage läuft das ähnlich. Fehlt eine einzelne Datei, so gegebenenfalls über rpmseek suchen, zu welchem Paket die Datei gehört, dann entsprechend nachinstallieren.

[basti12345]

Vielleicht könnt ihr mit ja helfen! Anhand von einem Beispiel!
Ich möchte mldonkey installieren!!

Dazu gibt es folgende Installationsanleitung!

nstallation

==================

-If you want to get up and running quickly and easily-

Compile mldonkey without GUI support
You have to have zlib, zlib-dev and m4 packages installed.

Mldonkey/> ./configure
Type in 'n' <enter> when it asks if you want to get lablgtk.
Mldonkey/> make depend
Mldonkey/> make

There is no additional 'make install' command. Copy the file 'mlnet'
(this is MLdonkey) to the folder where you've choosen to run MLdonkey.

Start 'mlnet'

Mlnet/> ./mlnet
Leave the terminal window open. MLdonkey is now running.

Open a browser and type in the URL http://localhost:4080 <enter>.
A web-based interface to MLdonkey appears. Certain ports enabling inbound
routing on your firewall/router need to be opened to fully use MLdonkey.
The Options tab in the web interface shows the ports.

-You're done!-

Some goodies (make_torrent, ed2k_hash) come with mldonkey, you can also
compile them using the additionnal command:

Mldonkey/> make utils

==================
There are additional ways besides the web interface to control Mlnet(MLdonkey).
- Compiling support for the 'mlgui' application while compiling MLdonkey
is one. This requires additional libraries, which, depending on your platform
and skill, may be easy or not so easy to add. The 'mlnet' application functions
fine without the GUI.
- Other applications are written by third-parties and available for specific
platforms. These vary in stability and functionality.

Compiling mldonkey with mldonkey_gui support:
-------------------

You have now two options to compile mldonkey:
- Individually install Objective-Caml 3.06 and LablGTK 1.2.?. Then, you can
compile mldonkey. The instructions are given below at '1)'.
- If you want to install ocaml and lablgtk only to compile mldonkey. You must
have a good internet access (you want mldonkey after all . You must have
"wget" installed. Then, run:

./configure -enable-batch

The configure script will download ocaml and lablgtk, compile and install them
locally so that they can be used to compile mldonkey. Steps below can be skipped
now. Be patient. Ocaml and lablgtk tools take a while to compile and install.

Note: At least 70 M of free disk space is required on the partition where mldonkey
is compiled.

------------------------------------------------------------------------
1) Installing required tools: Objective-Caml 3.06 and LablGTK 1.2.3 or 1.2.?

1.1) Objective-Caml 3.06 (from http://pauillac.inria.fr/caml)

~/tmp> tar zxf ocaml-3.06.tar.gz
~/tmp> cd ocaml-3.06

If you REALLY want to patch it:
~/tmp/ocaml-3.06> ./configure
~/tmp/ocaml-3.06> make world opt opt.opt
~/tmp/ocaml-3.06> make install

1.2) LablGTK 1.2.3 (from
http://wwwfun.kurims.kyoto-u.ac.jp/s...l/lablgtk.html)

~/tmp> tar zxf lablgtk-1.2.3.tar.gz
~/tmp> cd lablgtk-1.2.3
~/tmp/lablgtk-1.2.3> make configure
~/tmp/lablgtk-1.2.3> make
~/tmp/lablgtk-1.2.3> make opt
~/tmp/lablgtk-1.2.3> make install

2) Compiling mldonkey:

~/tmp/mldonkey> ./configure
~/tmp/mldonkey> make depend
~/tmp/mldonkey> make

You should now have 'mldonkey' (the daemon with edonkey/overnet support),
'mlnet' (the daemon with all network support) and 'mldonkey_gui' (the
interface) No 'make install' is provided.

You can disable all other p2p networks using the --disable-multinet option
with ./configure. Only edonkey support will then be compiled.

------------------------------------------------------------------------

Using mldonkey:
---------------

mldonkey binaries are normally distributed with only the content of the
mldonkey/distrib/ directory. Consequently, all documentation files on how to
use mldonkey are stored in this directory. You will also find default
configuration files in this directory, and in particular, a list of servers
for edonkey in the servers.ini file.

See the distrib/Readme.txt and distrib/FAQ.html files for more information
on how to use mldonkey.

Note that you should execute mldonkey in the distrib/ directory, where a
list of servers is present with other files. It will create other
configuration files in this directory. mldonkey_gui has its own configuration
file in the user directory (~/.mldonkey_gui.ini). I would advise you to move
mldonkey, mldonkey_gui, mldonkey_gui2 and mlchat to distrib/, then move this
directory where you want to put your downloads, and then remove mldonkey
sources.

You must NOT run mldonkey as root (or you should use the run_as_user
option to change the user after the port has been bound).

NOTES:
------
2002/12/18: To compile on MinGW
* configure: -enable-batch will not work, you must download and install ocaml
yourself
* if ocamlopt/gcc fails to generate mldonkey.exe, add '-verbose -S'
to the LIBS_opt in the Makefile. Use 'make &> log' to keep the
commands, edit the 'log' file and remove all the commands except
the 2 last 'as' and 'gcc' lines. Then use 'sh ./log' to rerun
these commands, that should work this way
* For a flawless compile these variables should be set
(OCAMLDIR means the root directory of the Ocaml binaries):
SET CAMLLIB=OCAMLDIR/lib
SET CAMLP4LIB=OCAMLDIR/lib/camlp4
SET OCAMLLIB=OCAMLDIR/lib
SET OCAMLRUNPARAM="l=256M"
* On the MLDonkeyworld forum is a great thread with information about
how to compile MLDonkey with MinGW:
http://mldonkey.berlios.de/modules.p...ewtopic&t=1363



Also erstmal sowiet ich das verstand3en habe brauche ich:

Objective-Caml 3.06, LablGTK 1.2.3
Erst dann kann ich mldonkey kompilieren!
Gut...
Soweit hab ich es ja noch verstanden...
Unter http://pauillac.inria.fr/cam bekomme ich z.b. ob-cam!!

Lieg ich da jetz zum beispiel richtig dass ich beim 3.07 "Source distribution" runterladen muss, weil ich suse linux habe oder?
Gut... ich habs entpackt jetzt finde ich dort eine readme!!


OVERVIEW:

Objective Caml is an implementation of the ML language, based on
the Caml Light dialect extended with a complete class-based object system
and a powerful module system in the style of Standard ML.

Objective Caml comprises two compilers. One generates bytecode
which is then interpreted by a C program. This compiler runs quickly,
generates compact code with moderate memory requirements, and is
portable to essentially any 32 or 64 bit Unix platform. Performance of
generated programs is quite good for a bytecoded implementation:
almost twice as fast as Caml Light 0.7. This compiler can be used
either as a standalone, batch-oriented compiler that produces
standalone programs, or as an interactive, toplevel-based system.

The other compiler generates high-performance native code for a number
of processors. Compilation takes longer and generates bigger code, but
the generated programs deliver excellent performance, while retaining
the moderate memory requirements of the bytecode compiler. The
native-code compiler currently runs on the following platforms:

Intel/AMD Pentium processors: PCs under Linux, FreeBSD, NetBSD,
OpenBSD, Windows, NextStep, Solaris 2, BeOS.
PowerPC processors: PowerMacintosh under MacOS X and LinuxPPC,
IBM RS6000 and PowerPC workstations under AIX 4.3
AMD64 (Opteron) processors: PCs under Linux.
Alpha processors: Digital/Compaq/HP Alpha machines under
Digital Unix/Compaq Tru64, Linux, NetBSD and OpenBSD.
Sparc processors: Sun Sparc machines under Solaris 2, NetBSD, Linux
Mips processors: SGI workstations and mainframes under IRIX 6
Intel IA64 processors: HP stations under Linux
HP PA-RISC processors: HP 9000/700 under HPUX 10
Strong ARM processors: Corel Netwinder under Linux

Other operating systems for the processors above have not been tested,
but the compiler may work under other operating systems with little work.

Before the introduction of objects, Objective Caml was known as Caml
Special Light. Objective Caml is almost upwards compatible with Caml
Special Light, except for a few additional reserved keywords that have
forced some renaming of standard library functions.

CONTENTS:

Changes what's new with each release
INSTALL instructions for installation
INSTALL.MPW infos on the Macintosh MPW port of Objective Caml
LICENSE license and copyright notice
Makefile main Makefile
README this file
README.win32 infos on the MS Windows 98/ME/NT/2000 ports of O.Caml
asmcomp/ native-code compiler and linker
asmrun/ native-code runtime library
boot/ bootstrap compiler
bytecomp/ bytecode compiler and linker
byterun/ bytecode interpreter and runtime system
config/ autoconfiguration stuff
debugger/ source-level replay debugger
driver/ driver code for the compilers
emacs/ Caml editing mode and debugger interface for GNU Emacs
lex/ lexer generator
maccaml/ the Macintosh GUI
ocamldoc/ documentation generator
otherlibs/ several external libraries
parsing/ syntax analysis
stdlib/ standard library
tools/ various utilities
toplevel/ interactive system
typing/ typechecking
utils/ utility libraries
yacc/ parser generator

COPYRIGHT:

All files marked "Copyright INRIA" in this distribution are copyright
1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 Institut National de
Recherche en Informatique et en Automatique (INRIA) and distributed
under the conditions stated in file LICENSE.

INSTALLATION:

See the file INSTALL for installation instructions on Unix, Linux and
MacOS X machines. For MS Windows, see README.win32.
For the MacOS 7, 8, 9, see INSTALL.MPW.

DOCUMENTATION:

The Objective Caml manual is distributed in HTML, PDF, Postscript,
DVI, and Emacs Info files. It is available on the World Wide Web, at

http://caml.inria.fr/

AVAILABILITY:

The complete Objective Caml distribution can be accessed through a Web
browser at

http://caml.inria.fr/

or by anonymous FTP:

host: ftp.inria.fr
directory: INRIA/caml-light

KEEPING IN TOUCH WITH THE CAML COMMUNITY:

There exists a mailing list of users of the Caml implementations
developed at INRIA. The purpose of this list is to share
experience, exchange ideas (and even code), and report on applications
of the Caml language. Messages can be written in English or in
French. The list has about 500 subscribers.

Messages to the list should be sent to:

caml-list@inria.fr

If you wish to subscribe to this list, please send a message to:

caml-list-request@inria.fr

with the single word "subscribe" in the body of the message.

Archives of the list are available on the World Wide Web at URL
http://caml.inria.fr/

The Usenet news groups comp.lang.ml and comp.lang.functional
also contains discussions about the ML family of programming languages,
including Caml.

BUG REPORTS AND USER FEEDBACK:

Send your bug reports by E-mail to:

caml-bugs@inria.fr

or report them using the Web interface to the bug-tracking system
at http://caml.inria.fr/bin/caml-bugs

To be effective, bug reports should include a complete program
(preferably small) that exhibits the unexpected behavior, and the
configuration you are using (machine type, etc).

You can also contact the implementors directly at caml@inria.fr.

und eine Install Readme!


Installing Objective Caml on a Unix machine
-------------------------------------------

PREREQUISITES

* The GNU C compiler gcc is recommended, as the bytecode
interpreter takes advantage of gcc-specific features to enhance
performance.

* Under HP/UX, the GNU C compiler gcc, the GNU assembler gas, and GNU make
are all *required*. The vendor-provided compiler, assembler and make
have major problems.

* Under MacOS X, before you begin, you must raise the limit on the
stack size with one of the following commands:

limit stacksize 64M # if your shell is zsh or tcsh
ulimit -s 65536 # if your shell is bash


INSTALLATION INSTRUCTIONS

1- Configure the system. From the top directory, do:

./configure

This generates the three configuration files "Makefile", "m.h" and "s.h"
in the config/ subdirectory.

The "configure" script accepts the following options:

-bindir <dir> (default: /usr/local/bin)
Directory where the binaries will be installed

-libdir <dir> (default: /usr/local/lib/ocaml)
Directory where the Caml library will be installed

-mandir <dir> (default: /usr/local/man/man1)
Directory where the manual pages will be installed

-prefix <dir> (default: /usr/local)
Set bindir, libdir and mandir to
<dir>/bin, <dir>/lib/ocaml, <dir>/man/man1 respectively.

-cc <C compiler and options> (default: gcc if available, cc otherwise)
C compiler to use for building the system

-libs <extra libraries> (default: none)
Extra libraries to link with the system

-no-curses
Do not use the curses library.

-host <hosttype> (default: determined automatically)
The type of the host machine, in GNU's "configuration name"
format (CPU-COMPANY-SYSTEM). This info is generally determined
automatically by the "configure" script, and rarely ever
needs to be provided by hand. The installation instructions
for gcc or emacs contain a complete list of configuration names.

-x11include <include_dir> (default: determined automatically)
-x11lib <lib_dir> (default: determined automatically)
Location of the X11 include directory (e.g. /usr/X11R6/include)
and the X11 library directory (e.g. /usr/X11R6/lib).

-tkdefs <cpp flags> (default: none)
-tklibs <flags and libraries> (default: determined automatically)
These options specify where to find the Tcl/Tk libraries for
LablTk. "-tkdefs" helps to find the headers, and "-tklibs"
the C libraries. "-tklibs" may contain either only -L/path and
-Wl,... flags, in which case the library names are determined
automatically, or the actual libraries, which are used as given.
Example: for a Japanese tcl/tk whose headers are in specific
directories and libraries in /usr/local/lib, you can use
./configure -tklibs "-L/usr/local/lib -ltk8.0jp -ltcl8.0jp"
-tkdefs "-I/usr/local/include/tcl8.0jp -I/usr/local/include/tk8.0jp"

-tk-no-x11
Build LablTk without using X11. This option is needed on Cygwin.

-no-tk
Do not attempt to build LablTk.

-no-pthread
Do not attempt to use POSIX threads.

-verbose
Verbose output of the configuration tests. Use it if the outcome
of configure is not what you were expecting.

Examples:
./configure -prefix /usr/bin
./configure -bindir /usr/bin -libdir /usr/lib/ocaml -mandir /usr/man/manl
./configure -cc "acc -fast" -libs "-lucb"
# For Sun Solaris with the acc compiler
./configure -cc "xlc_r -D_AIX43 -Wl,-bexpall,-brtl -qmaxmem=8192"
# For AIX 4.3 with the IBM compiler

If something goes wrong during the automatic configuration, or if the
generated files cause errors later on, then look at the template files

config/Makefile-templ
config/m-templ.h
config/s-templ.h

for guidance on how to edit the generated files by hand.

2- From the top directory, do:

make world

This builds the Objective Caml bytecode compiler for the first time.
This phase is fairly verbose; consider redirecting the output to a file:

make world > log.world 2>&1 # in sh
make world >& log.world # in csh

3- (Optional) To be sure everything works well, you can try to
bootstrap the system --- that is, to recompile all Objective Caml
sources with the newly created compiler. From the top directory, do:

make bootstrap

or, better:

make bootstrap > log.bootstrap 2>&1 # in sh
make bootstrap >& log.bootstrap # in csh

The "make bootstrap" checks that the bytecode programs compiled with
the new compiler are identical to the bytecode programs compiled with
the old compiler. If this is the case, you can be pretty sure the
system has been correctly compiled. Otherwise, this does not
necessarily mean something went wrong. The best thing to do is to try
a second bootstrapping phase: just do "make bootstrap" again. It will
either crash almost immediately, or re-re-compile everything correctly
and reach the fixpoint.

4- If your platform is supported by the native-code compiler (as
reported during the autoconfiguration), you can now build the
native-code compiler. From the top directory, do:

make opt
or:
make opt > log.opt 2>&1 # in sh
make opt >& log.opt # in csh

5- (Optional) If you want to give the native-code compiler a serious
test, you can try to compile the Objective Caml compilers with the
native-code compiler (they are compiled to bytecode by default).
Just do:

make opt.opt

Later, you can compile your programs to bytecode using ocamlc.opt
instead of ocamlc, and to native-code using ocamlopt.opt instead of
ocamlopt. The ".opt" compilers should run faster than the normal
compilers, especially on large input files, but they may take longer
to start due to increased code size. If compilation times are an issue on
your programs, try the ".opt" compilers to see if they make a
significant difference.

An alternative, and faster approach to steps 2 to 5 is

make world.opt # to build using native-code compilers

The result is equivalent to "make world opt opt.opt", but this may
fail if anything goes wrong in native-code generation.

6- You can now install the Objective Caml system. This will create the
following commands (in the binary directory selected during
autoconfiguration):

ocamlc the batch bytecode compiler
ocamlopt the batch native-code compiler (if supported)
ocamlrun the runtime system for the bytecode compiler
ocamlyacc the parser generator
ocamllex the lexer generator
ocaml the interactive, toplevel-based system
ocamlmktop a tool to make toplevel systems that integrate
user-defined C primitives and Caml code
ocamldebug the source-level replay debugger
ocamldep generator of "make" dependencies for Caml sources
ocamldoc documentation generator
ocamlprof execution count profiler
ocamlcp the bytecode compiler in profiling mode

and also, if you built them during step 5,

ocamlc.opt the batch bytecode compiler compiled with ocamlopt
ocamlopt.opt the batch native-code compiler compiled with ocamlopt
ocamllex.opt the lexer generator compiled with ocamlopt

From the top directory, become superuser and do:

umask 022 # make sure to give read & execute permission to all
make install

7- Installation is complete. Time to clean up. From the toplevel
directory, do "make clean".

8- (Optional) The emacs/ subdirectory contains Emacs-Lisp files for an
Objective Caml editing mode and an interface for the debugger. To
install these files, change to the emacs/ subdirectory and do

make EMACSDIR=<directory where to install the files> install
or
make install

In the latter case, the destination directory defaults to the
"site-lisp" directory of your Emacs installation.

9- After installation, do *not* strip the ocamldebug and ocamlbrowser
executables. (These are mixed-mode executables, containing both
compiled C code and Caml bytecode; stripping erases the bytecode!)
Other executables such as ocamlrun can safely be stripped.

IF SOMETHING GOES WRONG:

Read the "common problems" and "machine-specific hints" section at the
end of this file.

Check the files m.h and s.h in config/. Wrong endianness or alignment
constraints in m.h will immediately crash the bytecode interpreter.

If you get a "segmentation violation" signal, check the limits on the
stack size and data segment size (type "limit" under csh or
"ulimit -a" under bash). Make sure the limit on the stack size is
at least 4M.

Try recompiling the runtime system with optimizations turned off
(change CFLAGS in byterun/Makefile and asmrun/Makefile).
The runtime system contains some complex, atypical pieces of C code
that can uncover bugs in optimizing compilers. Alternatively, try
another C compiler (e.g. gcc instead of the vendor-supplied cc).

You can also build a debug version of the runtime system. Go to the
byterun/ directory and do "make ocamlrund". Then, copy ocamlrund to
../boot/ocamlrun, and try again. This version of the runtime system
contains lots of assertions and sanity checks that could help you
pinpoint the problem.


COMMON PROBLEMS:

* The Makefiles use the "include" directive, which is not supported by
all versions of make. Use GNU make if this is a problem.

* The Makefiles assume that make execute commands by calling /bin/sh. They
won't work if /bin/csh is called instead. You may have to unset the SHELL
environment variable, or set it to /bin/sh.

* gcc 2.7.2.1 generates incorrect code for the runtime system in -O mode
on some Intel x86 platforms (e.g. Linux RedHat 4.1 and 4.2).
If this causes a problem, the solution is to upgrade to 2.7.2.3 or above.

* Some versions of gcc 2.96 for the Intel x86 (as found in RedHat 7.2,
Mandrake 8.0 and Mandrake 8.1) generates incorrect code for the runtime
system. The "configure" script tries to work around this problem.

* On HP 9000/700 machines under HP/UX 9. Some versions of cc are
unable to compile correctly the runtime system (wrong code is
generated for (x - y) where x is a pointer and y an integer).
Fix: use gcc.


Danke
BastiIch weiss einfach jetzt nicht mehr was ich machen muss, wo ich anfangen muss, obs egal ist wenn ich irgendwas durcheinder bringe!
Und nie weiss ich was ich damit bewirke was mir am aller meisten zu schaffen macht!


Vielen Dank
Basti

[BloodyBullet]

Das nächste Mal, solltest du den Text verlinken.

MfG

[DERRICHTER]

Nimm die Kmldonkey-Rpm-Pakete von http://packman.links2linux.de, wenn Du Suse hast. Abhängigkeiten löst Du, indem Du fehlende Pakete von hier ftp://ftp.gwdg.de/linux/suse/apt/SuSE/ holst!

[basti12345]

Ich brauche jetzt für ocaml labltk!! Wenn ich ./configure mache, kommt die Fehlermeldung:

options for linking ...... not found
The "labltk" library: not found

Was muss ich denn da jetzt installieren?

[Tranalogic]

Ich würde dir Raten als Neuling zuerst mit RPM die Programme zu installieren (also RPM Pakete) und später mit dem kompilieren anfangen.

[basti12345]

ja aber da gibts keine rpm packete!!! Das ist ja das Problem. Und manchmal finde ich welche, aber dann nicht für suse linux 9.2!! Kann ich die, die für andere Linux Versionen gedacht sind denn auch installieren?

[BloodyBullet]

ja aber da gibts keine rpm packete!!! Das ist ja das Problem. Und manchmal finde ich welche, aber dann nicht für suse linux 9.2!! Kann ich die, die für andere Linux Versionen gedacht sind denn auch installieren?

Hier findest du viele vorkompilierte Programme:
http://www.rpmseek.com/index.html

MfG

[MATI]

Hi Basti,
ich persönlich finde www.pbone.net besser als www.rpmseek.com.
Dort findet man eine größere Auwahl und ich finde die Beschreibungen auch besser.
Wenn du einfach in den RPM-Suchmaschinen dein Paket welches du brauchst um Abhängigkeiten zu lösen eingibst dann findet er meistens schon was (zur NOt auch mal googlen fürs Paket)
Dann kannst du meistens auch deine Distributionsspezifische Auswahl bekommen....steht dann halt was weiß ich so ein Paketname wie: abcde_suse_9.2.rpm oder so.

Wenn du fragen hast poste! Wir helfen gern.
Ach ja....zu dem Ellenlangen Posting....sowas lesen die wenigsten durch. Versuch einfach immer zu posten was du schon gemacht hast und wo deine Probleme liegen dann kriegst du am schnellsten hilfe.

MFG

[stan]

ja aber da gibts keine rpm packete!!! Das ist ja das Problem. Und manchmal finde ich welche, aber dann nicht für suse linux 9.2!!

Nimm die Kmldonkey-Rpm-Pakete von http://packman.links2linux.de, wenn Du Suse hast. Abhängigkeiten löst Du, indem Du fehlende Pakete von hier ftp://ftp.gwdg.de/linux/suse/apt/SuSE/ holst!

Ääähm?
Wenn ich die Anweisungen von DERRICHTER befolge komme ich hierher: http://packman.links2linux.de/?action=451 Das ist doch eindeutig ein Paket für deine Distri, oder???

Bitte lies Dir die Beiträge genau durch, bevor Du postest.

Gruß,

[DERRICHTER]

@basti12345: siehe Thread "labltk" (sprich die von Dir gesuchten Programme sind alle als RPM-Pakete für Suse 9.2 vorhanden!).