Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SASL_PATH no longer has any effect but is still documented #852

Open
flowerysong opened this issue Aug 3, 2024 · 0 comments
Open

SASL_PATH no longer has any effect but is still documented #852

flowerysong opened this issue Aug 3, 2024 · 0 comments

Comments

@flowerysong
Copy link
Contributor

In 79827fb (part of #745) SASL_PLUGINDIR replaced SASL_PATH as the environment variable used to configure the plugin directory at runtime. It's not clear that this was a deliberate change or what motivated it, since it's not mentioned in the commit message.

SASL_PATH is still referenced multiple times in the documentation, e.g.

Note that the library can use the environment variable SASL_PATH to locate the directory where the mechanisms are; this should be a colon-separated list of directories containing plugins. Otherwise it will default to the value of `--with-plugindir` as supplied to `configure` (which itself defaults to `/usr/local/lib`).
and
Note that the library can use the environment variable SASL_PATH to locate the

It also still has a vestigial presence in configure.ac, though nothing references this definition:

#define SASL_PATH_ENV_VAR "SASL_PATH"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant