[Bug 689936] New: SLPP for totem(?)
https://bugzilla.novell.com/show_bug.cgi?id=689936 https://bugzilla.novell.com/show_bug.cgi?id=689936#c0 Summary: SLPP for totem(?) Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: vuntz@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- Totem now comes with a library. SLPP magic, maybe? It might be useful when we update to a new incompatible library version, to smooth upgrades. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c1
Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c
Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c2
Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c3
Bjørn Lie
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c4
Vincent Untz
looking closer into this request, I'm not sure this actually makes sense: - Only totem plugins seem to make any sense out of libtotem => Those plugins will require totem in the 'right version' anyway, thus parallel installing of libtotem is not beneficial / functional.
in my opinion, we should not split this lib out.
The gain for an update 'might' be for the package manager, but it would very likely render the system unstable when running totem.
My initial idea was really: a) totem-plugin-foo requires libtotem.so.0 (or totem 3.4) b) we update totem and it now ships libtotem.so.1 c) zypper will ask the user what to do: remove totem-plugin-foo or keep old totem And we don't want c. How can we fix this without SLPP? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c5
Dominique Leuenberger
My initial idea was really: a) totem-plugin-foo requires libtotem.so.0 (or totem 3.4) b) we update totem and it now ships libtotem.so.1 c) zypper will ask the user what to do: remove totem-plugin-foo or keep old totem
And we don't want c.
How can we fix this without SLPP?
to my knowledge, this only works by ensuring totem-plugin-foo is updated to a new version / linked aaginst libtotem.so.1 as well. If not, we would end up with this situation in memory (After updating totem): Start totem. It links itself to libtotem.so.1 Totem loads plugin-foo, which links and thus loads libtotem.so.0 I am almost certain that this will clash in ANY situation. The exported symbols are not versioned. Thus I'm not even sure (c) would not be the best option to propose. Anything else results in crashes when starting totem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c6
--- Comment #6 from Vincent Untz
If not, we would end up with this situation in memory (After updating totem): Start totem. It links itself to libtotem.so.1 Totem loads plugin-foo, which links and thus loads libtotem.so.0
Nearly sure that totem wouldn't load plugin-foo since the .plugin file has a IAge field, and it wouldn't match with the new version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c7
--- Comment #7 from Dominique Leuenberger
(In reply to comment #5)
If not, we would end up with this situation in memory (After updating totem): Start totem. It links itself to libtotem.so.1 Totem loads plugin-foo, which links and thus loads libtotem.so.0
Nearly sure that totem wouldn't load plugin-foo since the .plugin file has a IAge field, and it wouldn't match with the new version.
I remember we had some discussion about that on IRC around the time May... we ended up concluding that libtotem.so.0 is not the plugin loading lib... But I don't remember what our conclusion was on the way forward. Does SLPP make sense here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c
Dominique Leuenberger
https://bugzilla.novell.com/show_bug.cgi?id=689936
https://bugzilla.novell.com/show_bug.cgi?id=689936#c8
Vincent Untz
participants (1)
-
bugzilla_noreply@novell.com