Why is the prefix of the KDE packages changed? (answered)

[JohnW_57]

Why is the prefix of the KDE packages changed?

Example kde-libs:
old: kde-libs4 (with the suffix) 4.6.5-1pclos2011
new: kde-libs  (with the suffix) 4.8.2-1pclos2012

What happens if the update was from kde-libs4 4.6.5-1pclos2011 to kde-libs4 4.8.2-1pclos2012

This looks for me a more logical upgrade path to me?

JohnW

[Neal ManBear]

What's wrong with dropping the "4?"     

[gseaman]

What's wrong with dropping the "4?"     

I've always assumed that when a package had a number before the "-", it was to allow different versions to install on the same system, like gtk+2.0 and gtk+3.0. Since, having more than one version of kde installed at once is to complex, there is probably no need for the "4". 

Galen

[JohnW_57]

Maybe stupid thinking of me?
If you don't removing the KDE 4.6.5 packages  you can start a 4.6.5 session and in this session you can start a 4.8.2 session when changing user like someone have multiple desktops have installed on his system?

Didn't try it when updated to 4.8.2 

JohnW

[muungwana]

I think the "4" was there to distinguish kde3 libs and kde4 libs.This was relevant when people where transitioning to kde4.

since nobody will see "kdelibs" and wonder if its kde3 or kde4 library,the "4" is no longer necessary. It doesnt hurt though keeping and its future proof to the transition to kde5.

[Archie]

For whatever reasons the "4" was affixed to the KDE components, it was that most major distros use it. The "4" has been dropped by these major distros as well. It was not just something we decided to do ourselves but patterned over what others have already been doing. It would also make searching at rpm.phone uniform and easier.

muungwana is right. It doesn't hurt to keep it and could be useful in the transition to KDE5. And though often the suffixes are hidden, we still have 4.9.4 to think of how we can facilitate the transition.

Peace and much respect,
Archie

[JohnW_57]

The reason why I ask this question because Synaptic doesn't, didn't see as updated packages but as new ones.

JohnW

[Archie]

The reason why I ask this question because Synaptic doesn't, didn't see as updated packages but as new ones.

JohnW

And that is probably for the better, and have saved many users from borking their installs because from 4.6.5 to 4.8.0 caused many breakage that were only fixed during the 4.8.0 tests. KDE 4.8.2 was much better in ways but we still don't have a foolproof upgrade path that is painless. There are ideas floating around and one is likely to be a unanimous decision.

[JohnW_57]

The reason why I ask this question because Synaptic doesn't, didn't see as updated packages but as new ones.

JohnW

And that is probably for the better, and have saved many users from borking their installs because from 4.6.5 to 4.8.0 caused many breakage that were only fixed during the 4.8.0 tests. KDE 4.8.2 was much better in ways but we still don't have a foolproof upgrade path that is painless. There are ideas floating around and one is likely to be a unanimous decision.

Archie, thx for the info!  

JohnW