Re: [M-dev] alephone directory argument and ALEPHONE_DATA

[Gregory S. <wo...@tr...>]

On Fri, May 27, 2011 at 11:52 AM, Jeremiah Morris <jm...@wh...> wrote:
>> So, *nix builds (non Mac OS X) only:
>>
>> ALEPHONE_DATA nonempty, no directory_argument given:
>> search path = ALEPHONE_DATA
>>
>> ALEPHONE_DATA nonempty, directory_argument given:
>> search path = directory_argument:ALEPHONE_DATA
>>
>> ALEPHONE_DATA empty, no directory_argument given:
>> search path = prefix/AlephOne:~/.alephone
>>
>> ALEPHONE_DATA empty, directory_argument given:
>> search path = directory_argument:~/.alephone
>>
>> Is that right?
>
> I was thinking:
>
> ALEPHONE_DATA nonempty, no directory_argument given:
> search path = prefix/AlephOne:ALEPHONE_DATA
>
> ALEPHONE_DATA nonempty, directory_argument given:
> search path = directory_argument:ALEPHONE_DATA
>
> ALEPHONE_DATA set to empty string, no directory_argument given:
> search path = prefix/AlephOne
>
> ALEPHONE_DATA set to empty string, directory_argument given:
> search path = directory_argument
>
> ALEPHONE_DATA not set, no directory_argument given:
> search path = prefix/AlephOne:~/.alephone
>
> ALEPHONE_DATA not set, directory_argument given:
> search path = directory_argument:~/.alephone
>
> This collapses to two rules:
>
> 1) if ALEPHONE_DATA is not set, act as if it's set to ~/.alephone
> 2) if no directory argument is given, act as if prefix/AlephOne was given
>
> To completely control the search path, one needs to both set ALEPHONE_DATA and set a directory argument, which is a potential drawback and change of behavior in the first case. However, it does allow you to override either of the two hardcoded paths independently.

Any preference, Glen?

Gregory