The recent vote on the inclusion of OpennSSL in Sage has shown that some Sage developers [wished](https://groups.google.com/d/msg/sage-devel/fE45025Wphs/mKdCAeNhAgAJ) to keep the ability to build Sage without dependence on this contentious library.
I think that this can be implemented, thanks to Git, in the following manner : * Prepare a branch (let's say `anchorite`). * Follow the [Trac ticket](https://trac.sagemath.org/ticket/24107) aiming at the inclusion of OpenSSL * At this ticket merge into Sage, revert the pertinent commits in `anchorite` * At each point you want to release, merge with the branch you wish to reach to in `master` or `develop`, and reverse again. * If new additions or patches rely on the presence of OpenSSL, add them to your set of patches to be reversed, rinse and repeat... In short, the delta between `master` or `develop` and `anchorite` will be the sum of patches reversal involvig OpenSSL. This is easy to do for people using git as thei source. The problem is not so simple to release tarballs or binaries : a synchronization with the release manager is necessary. And I haven't the foggiest idea on how to proceed, for lack of knowledge of the release process. No ,proposal ticket (yet), since this is mainly an organizational issue... Your inputs, please ? -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
