[xcvb-devel] CL_SOURCE_REGISTRY question

[Faré]

Dear Peter,

>> What should XCVB do in these cases of how CL_SOURCE_REGISTRY is set:
>>
>> CL_SOURCE_REGISTRY=
>> CL_SOURCE_REGISTRY=. ;; or some other relative path
>> CL_SOURCE_REGISTRY=/absolute/but/nonexistent/path
>> CL_SOURCE_REGISTRY=/a/good/path
>
Are you trying to determine what XCVB is actually doing, or what it
"should" be doing?

Note that XCVB delegates most of the handling of CL_SOURCE_REGISTRY to
ASDF, so that the two should produce consistent results.

> Barring any complaints, here is a proposed semantic:
>
> CL_SOURCE_REGISTRY=
>        Ignored. Systems can be discovered through other means too.
>
That's what's happening. An empty string means "recurse to inherited
configuration".

> CL_SOURCE_REGISTRY=. ;; or some other relative path
>        Fail with an error that it should be an absolute path.
>
Currently, it fails indeed for want of an absolute path.

> CL_SOURCE_REGISTRY=/absolute/but/nonexistent/path
>        Work properly, there are just no systems discovered under it.
>
Yup.

> CL_SOURCE_REGISTRY=/a/good/path
>        Works properly, systems found.
>
Yes. Though you probably want // at the end to recurse through subdirectories.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
If money is your hope for independence you will never have it. The only real
security that a man will have in this world is a reserve of knowledge,
experience, and ability. — Henry Ford