Re: Some thoughts on SuSE package management

From: Michael Pokraka (junkmail_at_quirky.me.uk)
Date: 04/14/04


Date: Tue, 13 Apr 2004 23:04:25 +0100

Arun Dev wrote:
> 1. I have installed SuSE 9.0 and later changed the "Installation
> source" to the local sunsite mirror.
> Wenn I fetch the kernel it carries a version 2.4.21-144 but
> my running version gives 2.4.21-199-default. What does that
> mean? If I compile my own kernel am I going _back_?

Yes, as your local sunsite mirror is the original 9.0 distribution, which
shipped with 2.4.21-144. It's fixed that way.

> I believe SuSE hat changed the kernel source quite a lot,
> otherwise where does "make cloneconfig" come from?
> (I like the idea though).
Yes, there are a few tweaks, but I'm not the best person to answer that.
Agreed, cloneconfig id nifty :)

>
> 2. Now wenn I update packages it goes to a Server in Germany so
> I believe the packages in the local sunsite server are frozen
> at the release of 9.0. Update simply means uninstall the
> original and install the latest from the German server.
> Am I right?

Partly - see answer to 1. Yast is a bit like urpmi. The update (and there's
a list of servers) will basically do a rpm -U (I think).

>
> 3. How does YaST handle installation of external rpm's? Say
> if I do rpm -i somepackage.rpm and it all goes well, does
> YaST know about it?
>
Yep, yast uses rpm in some fashion or other. In fact you should use yast
instead of RPM. From 'man yast':
      -i, --install <package>
              Install an RPM package. The package can be a single short
package name (e.g. gvim)
              which will be installed with dependency checking, or the full
path to an rpm package
              (e.g /tmp/gvim.rpm) which will be installed without dependency
checking.

Suggestion if you have the space - I copied the DVD onto my HD and just
install locally. The KDE desktop has a 'Suse update checker' running by
default which will tell you when anything is available. I do suggest
running update after any major package installations.

Cheers
Mike



Relevant Pages

  • Re: konqueror-yast problem after upgrade from 8.2 to 9.0
    ... >> information and there is no button anymore to install the package. ... > You can go to file associations and associate rpm with yast. ...
    (alt.os.linux.suse)
  • Re: An error on each rpm ??
    ... > Since some weeks, each time i use Yast to install something, at the end ... I go directly to rpm. ... the new updated package DOES contain that library that rpm ... So I forced the install with "rpm -U --nodeps" ...
    (alt.os.linux.suse)
  • Re: installation from source: best practice ?
    ... those that exist in YaST sources, ... I'll look for an RPM of the package. ... place of the 'make install' step. ...
    (alt.os.linux.suse)
  • Re: logging in as root while running a non-root profile
    ... do 'yast -i package.rpm' And when it is a package on ... the instalation medium, just 'yast -i package' will do without the ... versiun and rpm part. ...
    (alt.os.linux.suse)
  • [PATCH 1/2] kbuil: add deb-pkg target
    ... # To prepare kbuild for more kernel packaging formats move all packaging ... # In top-level Makefile introduce generic support for all package ... Included the old rpm target for backward ... # and builddeb scripts. ...
    (Linux-Kernel)