[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Feature request: setting env vars for binary wrappers

From: Ralf Wildenhues
Subject: Re: Feature request: setting env vars for binary wrappers
Date: Fri, 18 Apr 2008 21:03:46 +0200
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

* Roumen Petrov wrote on Fri, Apr 18, 2008 at 08:53:12PM CEST:
> In some cases application depend from other services.
> In this case a specific to project wrapper script has to run services,  
> to check if service is run, to run project application and when  
> application finish to stop service. The test can be run from makefile.

With all due respect, but I think you haven't understood the problem
case Behdad is trying to solve.

It's very simple: packages have a test suite, or developers merely want
to run uninstalled programs, before they install them (in a new place,
or overwriting earlier versions of the programs and libraries).  In
order to ensure the uninstalled program uses only other uninstalled
stuff, one typically sets some variables, for example $PATH,
$LD_LIBRARY_PATH (or equivalents on other systems), tst_aclocaldir (this
is specific to the Libtool package itself), ...

The LD_LIBRARY_PATH thing (but portable) is already handled by libtool.
Why should it not also handle other variables, given that it would be
*very easy to do*?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]