Re: [Tack-devel] ACK_HOME and em_path

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

On Fri, Mar 08, 2019 at 08:09:00PM +0100, u-...@ae... wrote:
> > The easiest way i see is  to have em_path.h to contain all important directory defines directly relative to the root directory (either the environment variable or hard coded path) this generated at build time, so we can support both, and it has practically no impact on existing codes? What do you think?
> 
> It sounds good, to define all paths so that they are derived at run time,
> but isn't this already the case? (not looking at the source right now)

I now checked with the (5.5) code and it looks exactly like what you
describe: there is a default path defined at build time (possible to
be overriden at run time) and one relative path.

Which other directory defines you suggest to introduce there and why?

I can only guess that this was for the various system administration
tastes' sake (?)

If correct, it would mean complicating the compiler for no reason.

Please keep the structure straightforward, consistently documented,
with as small connection to the system administration as possible.

*** The fewer assumptions, the less headache for all parties. ***

I appreciate your and David's efforts. That's why I care when precious
time is spent on dicussing how to best support something which is
marginally relevant, impossible to solve in general and at the same time
an easy task for independent external means in every particular case.

If not otherwise, it is far easier to map a single-file-tree software
to a particular storage structure than to adapt from a _differing_
non-trivial file structure.

Rune