Project

General

Profile

Feature #9662

envPrepend and friends to recognize and/or deal appropriately with MANPATH-like variables

Added by Christopher Green about 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
07/17/2015
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Duration:

Description

MANPATH and other variables such as TEXINPUTS allow the specification of priority relative to the system paths by the addition of an extra leading, trailing or embedded colon. Is there some way that envPrepend and friends could be made to deal with this either automatically or (via an appropriate option) manually? It is currently very difficult to set MANPATH appropriately from within a UPS table file in a way that can deal with all possible forms of an existing MANPATH (or not) without possibly losing access to system paths.

History

#1 Updated by Marc Mengel about 4 years ago

... and PathPrepend does not do what you want? I've usually found

EnvSetIfNotSet(MANPATH,:)
PathPrepend(MANPATH, ${UPS_PROD_DIR}/man)

to work pretty reliably...

#2 Updated by Lynn Garren about 4 years ago

Thanks Marc. We'll give that a try.

#3 Updated by Christopher Green about 4 years ago

Looks like that's a reasonable thing to do, and it works for git based on my tests. Is there a particular reason we don't do this for catman and man in the UPS package itself?

Lynn, there are quite a few products we can do this for -- we should update ssi-build directories where appropriate: see find /products -type d -name man.

#4 Updated by Marc Mengel over 2 years ago

  • Status changed from New to Closed


Also available in: Atom PDF