After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 434926 - Multilib conflicts with gst-launch-0.10 man page
Multilib conflicts with gst-launch-0.10 man page
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 0.10.13
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-01 15:59 UTC by Bastien Nocera
Modified: 2007-05-02 17:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2007-05-01 15:59:15 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
Comment 1 Tim-Philipp Müller 2007-05-02 16:47:00 UTC
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.
Comment 2 Tim-Philipp Müller 2007-05-02 17:10:10 UTC
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.

Comment 3 Bastien Nocera 2007-05-02 17:23:21 UTC
Yay! Thanks Tim.