Hi Jason, On 16 Apr., 19:35, Jason Grout <[email protected]> wrote: > If we do that, then we should definitely make the notebook not dependent > on the optional spkg or pyopenssl. Otherwise we have this weird > situation where a standard package depends on an optional package.
I think we could live with that situation. It is similar to what happens with gcc: Sage needs gcc; if the user is not able to provide an appropriate gcc by him/herself, then there is still the gcc package. And now, Sagenb needs libssl-dev; if the user is not able to provide the libssl development headers by him or herself, then there is still the openssl spkg. Cheers, Simon -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
