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 143377 - OMF can't be installed in non-default directory
OMF can't be installed in non-default directory
Status: RESOLVED FIXED
Product: yelp
Classification: Applications
Component: General
unspecified
Other All
: Normal normal
: ---
Assigned To: Shaun McCance
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-30 04:21 UTC by Fawad Halim
Modified: 2005-09-18 20:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Fawad Halim 2004-05-30 04:21:45 UTC
Yelp doesn't like OMFs installed in non-default prefixes. In the test system,
the prefix for yelp is /usr. The application is installed under /usr/local,
hence its omf is located in /usr/local/share/omf/foo. The omf file has been
registered with scrollkeeper-install (and the installation verified by grepping
the /var/lib/scrollkeeper files). However, yelp seems to completely ignore the
scrollkeeper index and looks for OMF files on its own. 

The installed documentation doesn't show up in the yelp browser in the category
specified. Running yelp under strace shows that it's looking for directories
under /usr/share/omf. Even symlinking /usr/local/share/omf/foo into
/usr/share/omf/foo and registering the doc doesn't work. yelp is looking for an
actual filesystem directory and won't accept the symlink.

As a result of this, unless the app is installed in the same prefix as yelp
(i.e. /usr), yelp doesn't pick up the OMF entry.
Comment 1 Shaun McCance 2005-01-09 21:56:29 UTC
This should be fixed in 2.9.
Comment 2 Kjartan Maraas 2005-01-12 13:40:26 UTC
Should be as in is already fixed? Or we should fix it for 2.9.x?
Comment 3 Shaun McCance 2005-01-12 21:45:15 UTC
Should be as in I'm pretty sure it's fixed.  It would be nice to get a
confirmation from somebody who was experiencing this.
Comment 4 Shaun McCance 2005-09-18 20:36:35 UTC
I'm pretty confident this is fixed.  Since I haven't heard any more about this,
I'm going to close the bug.