Le vendredi 08 juin 2007 à 10:26 +0200, Loïc Minier a écrit : > The broken design is in GnomeVFS too. The Gtk and Pango module systems > provide registries of the modules, while GnomeVFS does not. Fixing > GStreamer in a clean fashion will only be possible if GnomeVFS provides > such a registry; otherwise, starting GStreamer apps checking all > GnomeVFS modules will be slow because of the time to load all the *.so > files and to dlopen() them with all their shlibs.
Whoa? The gnome-vfs registry is far from being as clean as that of gtk and pango, but you can't say it doesn't exist. If you want the list of supported methods, you just have to read the /etc/gnome-vfs-2.0/modules/*.conf files. There is absolutely no need to dlopen the modules, you only have to check the module is present (because the .conf files are in /etc - not a good idea - they can be still here while the module is removed). > Plus, as I said, this would/could completely disappear from GnomeVFS > packages when dpkg triggers will be available. I would take care of > the transition since you seem to see it as a huge burden. Not so huge, but completely unnecessary, and made for implementing a broken solution (as touching libgstgnomevfs.so) in the end. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
