<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 127: New Default Environment Variable 'WRAPPER_CONF_DIR'</title><link>https://sourceforge.net/p/wrapper/feature-requests/127/</link><description>Recent changes to 127: New Default Environment Variable 'WRAPPER_CONF_DIR'</description><atom:link href="https://sourceforge.net/p/wrapper/feature-requests/127/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 18 Jan 2011 09:56:41 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/wrapper/feature-requests/127/feed.rss" rel="self" type="application/rss+xml"/><item><title>New Default Environment Variable 'WRAPPER_CONF_DIR'</title><link>https://sourceforge.net/p/wrapper/feature-requests/127/</link><description>Most Integrationsmethods  imply that the wrapper binary is in a predefined location in respect to wrapper.conf configuration file or other application files. This means with WRAPPER\_BIN\_DIR could all such files could be located. 
But to simplify a integration method where the wrapper \(binary\) files are at an independent location and only the wrapper.conf file is with the application it would be useful to have an WRAPPER\_CONF\_DIR predefined environment variable which can be used to locate the wrapper.conf directory and so the application without having the directory explicitly configured in the wrapper.conf

Please add such a variable which is set at startup of the wrapper to the path of the used wrapper.conf file. 
It would be also useful, if this variable could be used early at startup  in "\#include" statements</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">charly</dc:creator><pubDate>Tue, 18 Jan 2011 09:56:41 -0000</pubDate><guid>https://sourceforge.net1a62a25d5694acffea22af7aa43a6a95035662ea</guid></item></channel></rss>