GNOME Bugzilla – Bug 673994
deps-3.6: gstreamer has been branched
Last modified: 2012-04-13 06:41:07 UTC
Update brasero, since it fails to compile otherwise. The other packages should be checked and updated one by one, I didn't look at it, as long as it compiles...
Created attachment 211931 [details] [review] deps-3.6: gstreamer has been branched
Comment on attachment 211931 [details] [review] deps-3.6: gstreamer has been branched You should branch existing modules, instead of duplicated them to have 0.10/master versions. If possible, we won't have to support multiple gstreamer versions in a single gnome release.
(In reply to comment #2) > (From update of attachment 211931 [details] [review]) > You should branch existing modules, instead of duplicated them to have > 0.10/master versions. They are parallel installable, and the focus is really on 0.11/1.0. Applications should start to be ported, so it's best if both are available in jhbuild. > If possible, we won't have to support multiple gstreamer versions in a single > gnome release. I think this is a different goal. And the transition period have to exist anyway.
After some discussion with other r-t members, we agreethat is better to add the 0.11 modules to 3.6 without deleting the earlier ones Fixed in commit f1aae45938f7d59e52cb62a038c9bc76b9c4096b and 1396bdb2fab14ef7f23c80c5e7156f7cf2a9711f
Seriously? Even if we want to have several gstreamer in jhbuild (and that doesn't seem necessary now) this is the wrong way to do it, existing modules are expecting 0.10, the existing gst* modules should be branched, and if you really want, you can then add -1.0 variants.
Javier, the followup commits when you switch more modules to the -0.10 gstreamer modules show how wrong it is; I reverted all of those, branched gstreamer, and added -master variants to the -world moduleset. Marc-Andre, if applications should start to be ported, the best way is to get a clear announce on ddl, not changing jhbuild modulesets.