The key words are "within the Sage source"... ;-) More on this later (i'a bit overwhelmed right now).
-- Emmanuel Charpentier Le 3 déc. 2016 17:51, "Thierry" <sage-googlesu...@lma.metelu.net> a écrit : On Sat, Dec 03, 2016 at 02:50:19PM +0100, Emmanuel Charpentier wrote: [...] > Ok. So we might try the following sequence : > > 1) in a pristine, openssl-virgin VM, compile Sage, and test pip's > ability to work (test 0, negative, as you proved). > > 2) install Sage's openssl, test pip's ability (test 1) > > If test1 positive, we win. > > If test 1 is negative, as you think > > 3a) update Python (./sage -f python2), and re-test pip's ability (test > 2) > > if test 2 positive, we win (serendipitously). I will try this, but it is supposed to work already (this is why an optional openssl Sage package exists and is maintained). I think i do not understand why it let us win, since we can not distribute openssl tarball within the Sage source code anyway. Ciao, Thierry -- You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/sage-devel/92OdoUbBDbE/unsubscribe. To unsubscribe from this group and all its topics, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
