GNOME Bugzilla – Bug 434926
Multilib conflicts with gst-launch-0.10 man page
Last modified: 2007-05-02 17:23:21 UTC
You can't easily install the RPM for gstreamer i386 and x86-64, as they contain different data for the gst-launch-0.10 man page. This is the diff between the 2 versions: -Path of the registry file. Default is ~/.gstreamer-0.10/registry-x86_64.xml. +Path of the registry file. Default is ~/.gstreamer-0.10/registry-i686.xml. Would it be possible to replace this difference by a mention of ~/.gstreamer-0.10/registry-$(uname -i).xml instead? Reported downstream at: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=228317
uname -i returns 'unknown' here (feisty/x86) - how about uname -m? Since the information in the man page is correct in both cases (it is, isn't it?), this should really be solved at the packaging level somehow (IMHO). But then it's also silly to cause these kind of problems for very little gain, so if uname -m is fine too and no one else has any objections, I'll change it.
Nevermind, I shouldn't make things more complicated than necessary ;) 2007-05-02 Tim-Philipp Müller <tim at centricular dot net> * tools/Makefile.am: * tools/gst-launch.1.in: Don't create a customised man page based on the host architecture, describe the default registry path generically. That way the man page is the same for all architectures and packagers have one multilib issue less to deal with. Fixes #434926.
Yay! Thanks Tim.