It appears that the --entry=... option of install-info
may be broken; I noticed this because several RPM packages
that use /sbin/install-info ... --entry="..." failed to
actually install info entries into the info directory.
Examples are cvs and bison.
*** This bug has been marked as a duplicate of 5639 ***
I don't think that this should be considered a duplicate of
5639, since resolving 5639 (by, for example, changing the CVS
RPM to not use '--entry=...') does nothing to actually make
--entry=... actually *work*. Which is what this bug report
Fixing the symptoms in Redhat-packaged RPMs still leaves the
program buggy and any third party programs, packages, Makefiles,
etc that are relying on the documented functionality up a creek.
(Of course, Redhat may consider this an issue for the FSF to fix
and not something they can or want to patch in the mean time, in
which case close this bug again -- but please reassure us that
you're doing it for that reason.)
All the test cases I threw at it work correctly here. A test case would be much
appreciated. Please reporn if you find one
The following test case is ripped off from 'rpm -q --scripts bison':
grep -v bison /usr/info/dir >/tmp/dir
/sbin/install-info /usr/info/bison.info.gz /tmp/dir --entry="* bison:
(bison). The GNU parser generator."
grep bison /tmp/dir
(and observe that, verily, /sbin/install-info will not have added
anything, because the grep will produce no output.)
A similar test-case can be gotten from the RedHat 6.1 'rpm -q