Re: Accepted ways when upstream author insists on using MANPATH env var?
On Fri, Sep 08, 2000 at 08:57:47AM +0300, Shaul Karl wrote:
> This state of affairs contradicts section 3.9 of the policy.
>
> My current solution is to patch the programe with a conditional setting of the
> MANPATH:
>
> if {![info exists env(MANPATH)] || [string equal [string trim $env(MANPATH)]
> ""]} {
> set env(MANPATH) [ exec /usr/bin/manpath ];}
>
> What are the acceptable ways to handle similar situations? Is there a better
> way other then using /usr/bin/manpath?
That sounds like a good solution. We should make modifications
to programs to make them work within the Debian environment;
that's where Debian adds value versus compiling from source IMHO.
Regards
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
Reply to: