Bug 232771 - texdoc searches $TEXMF/doc -- should use $TEXMFDOCS
texdoc searches $TEXMF/doc -- should use $TEXMFDOCS
Status: CLOSED DUPLICATE of bug 232769
Product: Fedora
Classification: Fedora
Component: tetex (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jindrich Novy
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2007-03-17 08:49 EDT by George N. White III
Modified: 2013-07-02 19:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-17 10:42:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description George N. White III 2007-03-17 08:49:01 EDT
Description of problem: documentation is not found if system uses a non-default

Version-Release number of selected component (if applicable):

How reproducible: always

Steps to Reproduce:
1. add non-standard directory to TEXDOCS in texmf.cnf
2. texdoc fails to find the new documentation
Actual results:

Expected results:

Additional info:

Here is the patch posted to the tex-live list by Frank Küster:

Subject: [tex-live] texdoc should always use TEXDOCS


a Debian user has noticed that, although texdoc uses 'kpsewhich
--format="TeX system documentation"' and thus the $TEXDOCS variable for
its main work, the search mode accesses $TEXMF/doc directly and ignores
changes/additions in TEXDOC.

The following patch would make it more consistent:

--- src/Upstream-source/TeXLive/Build/source/texk/tetex/texdoc.orig	2007-03-
15 16:36:30.000000000 +0100
+++ src/Upstream-source/TeXLive/Build/source/texk/tetex/texdoc	2007-03-15 
16:37:20.000000000 +0100
@@ -140,7 +140,7 @@
   case $mode in
-      find `kpsewhich --expand-path='$TEXMF/doc' | tr : ' '` -type f -print |
+      find `kpsewhich --expand-path='$TEXDOCS' | tr : ' '` -type f -print |
         egrep $name

(too simple to be copyrightable, of course).
Comment 1 George N. White III 2007-03-17 10:42:15 EDT
Bugzilla gives error "invalid product name, press back", but the bug was 
entered anyway

*** This bug has been marked as a duplicate of 232769 ***

Note You need to log in before you can comment on or make changes to this bug.