[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-linux
Subject: Re: [kde-linux] Installing KDE from binary RPMs
From: Bogus Zaba <bogzab () blueyonder ! co ! uk>
Date: 2005-06-01 22:50:10
Message-ID: 429E3BA2.8020809 () blueyonder ! co ! uk
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
ne... wrote:
> On May 31, 2005 at 21:14, Steven Pasternak in a soothing rage wrote:
>
>> Bogus Zaba wrote:
>>
>>> This may be a really stupid question. I am running Suse 9.2 with KDE
>>> 3.3.0. I have today downloaded 104 RPMs which make up KDE 3.4.1.
>>>
>>> Clearly because of dependencies, they have to be installed in a
>>> certain order, but how do I know what the order is without lots of
>>> trial and error ?
>>
> Without using yast, apt, yum... you cannot.
>
>>> Supplementary stupid question : how do I persuade the Suse YAST
>>> installer to install the packages *alongside* existing software
>>> rather than replacing all the existing stuff which mainly works OK.
>>
> You don't. Even tho harddrives are cheap these days, you really do
> not need to have two copies of the same thing installed. However,
> from the command line, rpm works.
> [...]
>
>> folder where all of the rpms are (they all need to be in one folder).
>> Type 'rpm -Uhv --force ./*.rpm'. To take care of dependency problems
>> (most of them,
>
> Please do not give bad advice like this anymore without fully
> explaining the consequences of the '--force' flag. If the OP
> breaks his system, are you going to be there to fix it for him?
> The OP needs to run 'rpm -Uvh --test *.rpm' and for each dependency
> not satisfied, download the required rpm and repeat the process.
>
> N.Emile...
Thanks for the various advice - I pieced together a way of doing it
which seems to have worked. In case others find this useful :
* it was a mistake to try and install the packages by simply
double-clicking the rpm files and invoking YAST that way - that
was giving me lots of dependency problems.
* Much better to start up YAST as super-user and do as advised in
one fo the posts above - change the installation source to the
directory where all my downloaded rpms were sitting. YAST then
nicely marks all the already-installed packages by colour-coding
them, so you know what to update.
* An order which led to few dependency problems was : 1. Qt library
; 2. Kdelibs ; 3. Kdebase. After that order does not seem very
important and anyway YAST finds some rpms which are needed if you
go for a package which requires another rpm to work.
* Still not istalled due to dependency problems are some of the
*-develop rpms, eg kdelibs3-devel-doc-3.4.1-5.i586.rpm which have
unresolved dependencies - probably because when I installed my
original Suse installation I did not bother with a lot of the
source code packages.
btw - advice was good to just update and overwrite. No problems
encountered. I was just paranoid because so many posts on this list seem
to say "My xxxx stopped working when I upgraded to KDEx.x"
Bogus
[Attachment #5 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
ne... wrote:
<blockquote cite="midPine.LNX.4.63.0506010805390.882@mach1.guhvies.org"
type="cite">On May 31, 2005 at 21:14, Steven Pasternak in a soothing
rage wrote:
<br>
<br>
<blockquote type="cite">Bogus Zaba wrote:
<br>
<br>
<blockquote type="cite">This may be a really stupid question. I am
running Suse 9.2 with KDE 3.3.0. I have today downloaded 104 RPMs
which make up KDE 3.4.1.
<br>
<br>
Clearly because of dependencies, they have to be installed in a certain
order, but how do I know what the order is without lots of trial and
error ?
<br>
</blockquote>
</blockquote>
Without using yast, apt, yum... you cannot.
<br>
<br>
<blockquote type="cite">
<blockquote type="cite">Supplementary stupid question : how do I
persuade the Suse YAST installer to install the packages *alongside*
existing software rather than replacing all the existing stuff which
mainly works OK.
<br>
</blockquote>
</blockquote>
You don't. Even tho harddrives are cheap these days, you really do
<br>
not need to have two copies of the same thing installed. However,
<br>
from the command line, rpm works.
<br>
[...]
<br>
<br>
<blockquote type="cite">folder where all of the rpms are (they all
need to be in one folder). Type 'rpm -Uhv --force ./*.rpm'. To take
care of dependency problems (most of them, </blockquote>
Please do not give bad advice like this anymore without fully
<br>
explaining the consequences of the '--force' flag. If the OP
<br>
breaks his system, are you going to be there to fix it for him?
<br>
The OP needs to run 'rpm -Uvh --test *.rpm' and for each dependency
<br>
not satisfied, download the required rpm and repeat the process.
<br>
<br>
N.Emile...
<br>
</blockquote>
Thanks for the various advice - I pieced together a way of doing it
which seems to have worked. In case others find this useful :<br>
<ul>
<li>it was a mistake to try and install the packages by simply
double-clicking the rpm files and invoking YAST that way - that was
giving me lots of dependency problems. <br>
</li>
<li>Much better to start up YAST as super-user and do as advised in
one fo the posts above - change the installation source to the
directory where all my downloaded rpms were sitting. YAST then nicely
marks all the already-installed packages by colour-coding them, so you
know what to update.</li>
<li>An order which led to few dependency problems was : 1. Qt library
; 2. Kdelibs ; 3. Kdebase. After that order does not seem very
important and anyway YAST finds some rpms which are needed if you go
for a package which requires another rpm to work.</li>
<li>Still not istalled due to dependency problems are some of the
*-develop rpms, eg kdelibs3-devel-doc-3.4.1-5.i586.rpm which have
unresolved dependencies - probably because when I installed my original
Suse installation I did not bother with a lot of the source code
packages.</li>
</ul>
btw - advice was good to just update and overwrite. No problems
encountered. I was just paranoid because so many posts on this list
seem to say "My xxxx stopped working when I upgraded to KDEx.x"<br>
<br>
Bogus<br>
<br>
</body>
</html>
___________________________________________________
This message is from the kde-linux mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic