Re: SuSE updates policy?
From: David Wright (david_c_wright_at_hotmail.com)
Date: Sat, 29 Jan 2005 09:42:55 +0100
Marcin P. wrote:
> houghi wrote:
>> Marcin P. wrote:
>> Whatever floats your boat. SUSE does only security updates for pacjkages
>> they made.
> Do you mean that SuSE did not make KDE suplementary packages? I didn't
> know that.
>> If you use other ones, you need to update them yourself if
>> you so please. That is one of thereasons I never do an update unless I
>> really, really need a new function in a program or set of programs.
> Same as me, but I liked 3.3.2 because comparing to 3.3.0, it has some
> useful fixes to KHTML and Konqui (which is my primary browser).
>>> the question is - is there any SuSE-specific RPM building howto?
>> I just use checkinstall.
> Does it care of dependecies? It didn't when I have been using it some time
> ago. I prefer normal way of building RPMs with spec file and so on.
They aren't official updates. For SuSE 9.2, you get KDE 3.3.0 as the
standard package and SuSE will provide security and bug fixes to the 3.3.0
line until the expiry of the 9.2 distribution (after 2 years or so).
If you install a package from suplimentary, it is not a fully approved and
tested SuSE package, although it might have been compiled at SuSE, or by
enthusiasts. These packages are supplied without warranty or guarantee that
they will work on any given system.
They are usually fairly reliable, but once installed, you are responsible
for obtaining any bug fixes or security updates for those packages, as
opposed to YOU. YOU will only find updates for packages in the official
tree, there are no official "updates" in the supplementary tree.
In this case, as you are running a newer version of KDE; I would flag the
KDE 3.3.0 updates in YOU with the blocked flag (no entry symbol) and look
to see if similar patches are available for 3.3.2 - it might be that the
patch fixes problems which have already been resolved in 3.3.2, or they may
affect all versions of KDE 3.3.n, so you'll need to check what the issue
is, cross reference back to the KDE site and see if the issue is applicable
to 3.3.2 and try and find a patch for 3.3.2 if it is - start looking in the
supplimentary tree for updated packages.
If you want an easy life, stick with what is in the official tree, if you
want to experiment with newer versions, you just have to be aware that you
also take over the responsibility for maintaining them as well...