On 10/18/07, Michael Halcrow <[EMAIL PROTECTED]> wrote:
> Just a quick note about the OpenSSL token build; this is the behavior
> that I would like to see:

You forgot to tell what you expect :)

>
> If openssl-devel is installed and the user does not specify
> --enable-openssl for ./configure, build the OpenSSL token.

That's correct, right? you wished it to be default enabled.

> If openssl-devel is installed and the user specifies
> --enable-openssl for ./configure, build the OpenSSL token.

That's correct too, right?

> If openssl-devel is not installed and the user does not specify
> --enable-openssl for ./configure, do not build the OpenSSL token
> (right now, ./configure bombs out).

As openssl is enabled by default, it just like you specified --enable-openssl.

> If openssl-devel is not installed and the user specifies
> --enable-openssl for ./configure, bomb out.

As openssl is enabled by default, there is no point in specifying
--enable-openssl.

>From the above I guess you expect openssl to be auto detected and be
used or unused. But this tends of building optional components the
user don't wish to have and add dependencies to executable that are
not always required.

Having the user specify the --enable-X features and failing if there
is a missing requested feature dependency is the safest way to build a
package.

If you want openssl to be auto detected I can do this, just say so,
but I don't recommend. I think leaving openssl disabled as default
should be the right solution, so people need to enable it if they wish
to use the feature, failing if dependency is missing.

Best Regards,
Alon Bar-Lev.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
eCryptfs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ecryptfs-devel

Reply via email to