Re: [Tack-devel] ACK_HOME and em_path

[<u-...@ae...>]

On Thu, Mar 07, 2019 at 02:28:30PM +0100, David Given wrote:
> We do still need the hard-coded path as a fall back --- we can't require
> end users to set an environment variable just to run a normal binary. I
> think we're going to need to keep em_path.h to configure this.
> 
> On Thu, 7 Mar 2019 at 12:16 Carl Eric Codere via Tack-devel <
> tac...@li...> wrote:
> 
> > Greetings,
> >                 Ok! Message well received... simply using ACK_HOME with no
> > magic tricks then!!

Thanks Carl!

OTOH I have to agree with David, hardcoding a path where an application
looks for its resources is a traditional practice, a necessary fallback
when a dedicated variable is not available.

This is of course different from silently falling back on the hardcoded
paths if a resource is not found via a _set_ variable. The latter
would make it uncertain whether the intention to use a specific
instance succeded or not.

Regards,
Rune