Mailinglist Archive: opensuse-kde (218 mails)
| < Previous | Next > |
Re: [suse-kde] KDE 3.0.0 -> 3.0.3 update problem...
- From: Carl <quantum@xxxxxxxxxxx>
- Date: Mon, 2 Sep 2002 11:01:06 -0500
- Message-id: <200209021008606.SM00099@there>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 02 September 2002 01:11 am, you wrote:
> But I did like this with every package:
>
> First i rpm -U
> (No --nodeps)
>
> If the package was updated without dependency errors, then fine.
>
> If there were dependency errors, I would note the dependencies and rpm
> -U --nodeps the same package again, and then go on to rpm -U the
> dependency packages - same scheme.
That's actually a safer method than most people use. But supposedly with K
in Supplementary, all dependencies are there.
> I wonder.
> If I have a whole slew of packages installed that I want to update,
> and I'm not sure what packages those are, could I then update all
> installed packages in one command like this?:
>
> rpm -F --nodeps *.rpm
Don't use -F or -I.
Always use -Uvh to install anything. Most people go to the directory then
rpm -Uvh --nodeps * .
Ben recommends (and I do too):
Install base then dev then apps.
1. After each installation of a group such as base you should
run SuSEconfig.
2. After all three groups are installed you should remove these
things...
A. All KDE related directories and files in /tmp
B. .mcop in your home directory
C. The two temp files in .kde that are pointing to files
that you've removed in /tmp.
Some people here recommend an automatic dependency resolver for installing
rpms called apt. I looked at it and it is nice, but like afio it is too
complex, and thus fairly inaccessable to someone who is busy. (or
mathematically-challenged like me) I wish K's package manager actually
worked. I wish Suse would put out a hotshit backup utility, so we could be
in the 21st century, rather than tarring what we absolutely must have.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj1zi0oACgkQnQ18+PFcZJscTQCcDe7pDJCvFgJe8lDkJk1BEjM+
0jcAn3gknLQ5owJiJW7f4t8BNHpyzgWW
=cqAn
-----END PGP SIGNATURE-----
Hash: SHA1
On Monday 02 September 2002 01:11 am, you wrote:
> But I did like this with every package:
>
> First i rpm -U
> (No --nodeps)
>
> If the package was updated without dependency errors, then fine.
>
> If there were dependency errors, I would note the dependencies and rpm
> -U --nodeps the same package again, and then go on to rpm -U the
> dependency packages - same scheme.
That's actually a safer method than most people use. But supposedly with K
in Supplementary, all dependencies are there.
> I wonder.
> If I have a whole slew of packages installed that I want to update,
> and I'm not sure what packages those are, could I then update all
> installed packages in one command like this?:
>
> rpm -F --nodeps *.rpm
Don't use -F or -I.
Always use -Uvh to install anything. Most people go to the directory then
rpm -Uvh --nodeps * .
Ben recommends (and I do too):
Install base then dev then apps.
1. After each installation of a group such as base you should
run SuSEconfig.
2. After all three groups are installed you should remove these
things...
A. All KDE related directories and files in /tmp
B. .mcop in your home directory
C. The two temp files in .kde that are pointing to files
that you've removed in /tmp.
Some people here recommend an automatic dependency resolver for installing
rpms called apt. I looked at it and it is nice, but like afio it is too
complex, and thus fairly inaccessable to someone who is busy. (or
mathematically-challenged like me) I wish K's package manager actually
worked. I wish Suse would put out a hotshit backup utility, so we could be
in the 21st century, rather than tarring what we absolutely must have.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj1zi0oACgkQnQ18+PFcZJscTQCcDe7pDJCvFgJe8lDkJk1BEjM+
0jcAn3gknLQ5owJiJW7f4t8BNHpyzgWW
=cqAn
-----END PGP SIGNATURE-----
| < Previous | Next > |