On Fri, Apr 25, 2014 at 06:12:15PM +0200, Raymond Wooninck wrote:
On Friday 25 April 2014 08:57:13 Greg KH wrote:
I understand that, it's just something that
users are not used to doing
when doing a "normal" 'zypper dup' update.
Ok, then I guess the only way is (as I indicated already) that Tumbleweed
remains on KDE 4.12.4 as that the migration to Baloo doesn't fall under a
normal zypper dup update.
Then how are you going to handle the update for users when they move to
the next openSUSE release?
It is strange for me that this migration has been done
by people that are
running oS 12.3 and oS 13.1, but that we can not ask this from Tumbleweed
Again, how are 13.1 users going to handle this? How are 12.3 users
going to handle it? Tumbleweed should not be any different, right?
But Tumbleweed is your baby, so you have the right to
reject a possible
upgrade of KDE. If Tumbleweed users would be happy with this, I don't know.
But as agreed before KDE:Current will NOT be build against Tumbleweed as that
this would clash with the ideas behind Tumbleweed.
I want to update to the latest KDE, I just don't want to see people with
broken machines because they did not know the "special" upgrade steps.
Because really, almost no Tumbleweed user reads the Factory mailing
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org