Repositories for 5.8 SOHO

[Freeman]

Can someone tell me which are the correct repo's for VL 5.8 SOHO?

I can see by default in my Gslapt:
/packages-soho
/packages
/extra
/patches

Is there a difference between the packages and the packages-Soho??
And if I try upgrade everything, it tells me Glib, GTK+, Cairo, .. all need to be upgraded. Which is a very delicate thing to do I've experienced. Someone tried this?

[retired1af]

I've done the full upgrade/update. Only thing I've found that breaks is the login screen for KDE. And that's a quick fix by finding GlassLights-SOHO and moving it to opt/kde/share/apps/kdm/themes

[MikeCindi]

I've done the full upgrade/update. Only thing I've found that breaks is the login screen for KDE. And that's a quick fix by finding GlassLights-SOHO and moving it to opt/kde/share/apps/kdm/themes

The way to avoid this is to not select (or de-select) KDE-Custom when you do a "full update" (http://www.vectorlinux.com/forum2/index.php?topic=3072.0). Just thought you might like to know.

@Freeman: I have done the full update several times without any problems except as retired1af has mentioned. The last time I did this I made the above "de-selection" and absolutely had no problems. As for the difference between packages-soho and packages I suspect that there may be certain packages that have been customized/optomized for SOHO or std Gold in the respective repositories.
HTH,
Mike

[Freeman]

Thanks guys for the tips!

I'll try it now, to upgrade it all except KDE-custom. There is one strange thing in the naming string off Pidgin.

Installed one is: Pidgin-2.0-i586-2VL58
The one for upgrade is: Pidgin-2.0.0-i586-1VL5.8

I think the installed is the newest. So I'll keep that one..

[JohnB316]

---snip---
Installed one is: Pidgin-2.0-i586-2VL58
The one for upgrade is: Pidgin-2.0.0-i586-1VL5.8
---snip---

This reply is more directed toward packagers. We need to be consistent in our version numbers when packaging. For example, if the source tarball version is 2.0.0, then any packages built from that tarball need to be consistent. Otherwise, updates can become a problem. Keep this in mind when building packages.

Thanks,
John