On Tue, Jul 16, 2019 at 1:13 AM François Bissey <frp.bis...@gmail.com> wrote: > > My contingency plan for sage-on-gentoo is > sed “s:@ARB_LIBRARY@:arb:” src/sage/env.py.in > src/sage/env.py > Replace “arb” and the paths with what is appropriate for your distribution.
alternatively I can store an environment variable in src/bin/sage-env-config (which, as you know, is also created by ./configure :-)) and then access it from src/sage/env.py to populate ARB_LIBRARY This would avoid creating src/sage/env.py.in > > > On 16/07/2019, at 12:04 PM, François Bissey <frp.bis...@gmail.com> wrote: > > > > I will not give it a positive review. I won’t prevent other people to do so. > > But I will not put my name on this. > > > > François > > > >> On 16/07/2019, at 12:02 PM, Dima Pasechnik <dimp...@gmail.com> wrote: > >> > >> One way or another, we need to move forward on > >> https://trac.sagemath.org/ticket/27270 > >> --- if you have a better solution than there, implement it, if not, > >> accept what it already provided. > >> > >> On Mon, Jul 15, 2019 at 11:31 PM François Bissey <frp.bis...@gmail.com> > >> wrote: > >>> > >>> For those not reading the ticket. > >>> Dima: > >>> well, I don't see a point of not running ./configure. Perhaps it was > >>> fashionable in Python world 10-15 years ago :-) > >>> > >>> My answer: > >>> It is an interesting comment about configure. Unfortunately, as far as I > >>> know running configure > >>> for a python project is still not a done thing. It doesn't mesh with the > >>> other elements of the > >>> python toolchain. There is certainly room for some configurability option > >>> in sage in regards to > >>> the optional libraries. But autotool's configure is definitely not the > >>> python way. Apart from > >>> cypari I cannot think of another python package using configure. > >>> > >>> Let's be honest, a small configure script for sage's optional stuff and > >>> the possibly unusual stuff > >>> would be fine to run. The full configure script for the whole of the > >>> distribution is inappropriate. > >>> It all goes back, once again, to "sagelib" being treated special instead > >>> of as a normal package. > >>> So many things would have to click in place once you do that. Other > >>> superbuild systems like the one > >>> for paraview don't treat the main target in a special way like sage's > >>> does. > >>> > >>> — > >>> François > >>> > >>>> On 16/07/2019, at 10:15 AM, François Bissey <frp.bis...@gmail.com> wrote: > >>>> > >>>> > >>>> > >>>>> On 16/07/2019, at 10:11 AM, arojas <nqn1...@gmail.com> wrote: > >>>>> > >>>>> > >>>>> > >>>>> El martes, 16 de julio de 2019, 0:07:19 (UTC+2), François Bissey > >>>>> escribió: > >>>>> > >>>>> And here I don’t run configure at all in sage-on-gentoo. I only use > >>>>> python standard > >>>>> tools to build the sage library itself. I could fix it but this is an > >>>>> annoyance I don’t need. > >>>>> > >>>>> François > >>>>> > >>>>> Neither do I - but with this patch there is no choice > >>>> > >>>> The choice is manual. You process the `env.py.in` manually in your > >>>> preparation > >>>> phase. Which is terrible of course but better than running configure. > >>>> And since I am building multiple python having to run configure is > >>>> really a pain > >>>> in the ***. > >>>> > >>>> François > >>> > >>> -- > >>> 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. > >>> To view this discussion on the web visit > >>> https://groups.google.com/d/msgid/sage-devel/820236E3-2C69-460E-94F9-7140C1AFA911%40gmail.com. > >>> 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. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/sage-devel/CAAWYfq2fzJ2u5SLcgNTZKnuCnEtYaY%2Bb%3DYgXCWpfF%2Byb7D3F7g%40mail.gmail.com. > >> 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/F3A5787A-7136-487A-A91A-6260654203AA%40gmail.com. > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq3EDqu71PLodL-4pkN-PhMnwoscCAnPfjVrGfkRJPeuOw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
