Mailinglist Archive: opensuse-kde (310 mails)

< Previous Next >
Re: openSUSE KDE team (was Re: [opensuse-kde] Missing package/update in KDF)
Am Mittwoch, 19. September 2012, 10:47:18 schrieb Nico Kruber:
On Tuesday 18 Sep 2012 21:14:55 Christian Trippe wrote:
2.) How to deal with packages not being part of KDE SC, e.g. amarok?
Here my personal opinion would be that as KRxy would be used as a devel
project also only bugfix release should be allowed.

That is easier said than done, because e.g. amarok and digicam don't really
offer bugfix releases - during the last official releases, not only bugfixes
were introduced, but also new features.

Since a potential bug only influences that particular application, it is not
as big of a deal as a bug in a kde lib or kwin etc...
This is similar to the Firefox,Thunderbird release cycle for which new
versions are also shipped in openSUSE:Update.


Sure I know this. It was more a meant like this:
If you want to use KR:xy as a devel project for updates for an openSUSE
release you should only update, e.g. amarok in this repo, if you really are
fine to release this also as an online update. Otherwise this workflow will not
work for non SC packages.

I agree with you that as this only effects one specific application and is
easily to revert one can probably accept it. But it is IMHO also more likely
to cause new bugs when doing this, see e.g
https://bugzilla.novell.com/show_bug.cgi?id=780628 for an amarok 2.6 bug on
plain 12.2 which is not there with 2.5.
So maybe a general rule of thumb how to handle this non-SC apps would be good.

Christian


--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-kde+owner@xxxxxxxxxxxx

< Previous Next >