Does sage need a purpose-built pari/gp? Ideally, configuring sage to use an external pari/gp would mean that sage just compiles/links using externally provided header files and libpari.so (and perhaps know where the gp executable is provided).
When sage is being rebuilt, it could take the modification dates of include/pari/* and libpari.so as a cue to rebuild the modules that depend on those. It could keep a timestamp file itself to detect this. Surely cypari has pari as a dependency, and doesn't supply it itself? Then someone who wants to develop both pari and sage could point sage at the local development pari and use sage -b or make build to bring sage in line with the local pari developments. -- 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.
