On Fri, Sep 27, 2019 at 8:01 PM John H Palmieri <jhpalmier...@gmail.com> wrote: > > I have been testing new versions of Simon King's p-group cohomology package. > The current version doesn't work with Python 3, and he has been working > (#28414) to fix this. My workflow: > > check out his git branch > run ./sage -f -c p_group_cohomology > report any issues > check out develop branch > > > Here is the problem: if step 2 works (which it has been recently), then > `build/make/Makefile` gets modified, adding p_group_cohomology to the list of > installed packages. When I switch back to the develop branch, then (since I > am using a Python 3 build of Sage), Sage doesn't build any more, because it > tries to build the broken version of the p_group_cohomology package. So then > I do > > "make p_group_cohomology-clean" > > but this does not change `build/make/Makefile` and so it does not fix the > problem. I can either edit the Makefile by hand or rerun ./configure. So here > are some questions: > > Is "sage -i PKG" or "sage -f PKG" the preferred way to install an optional > package? That's what our Developer's Guide says. Or should I be using "make > PKG", which does not modify "build/make/Makefile"? > Assuming I should keep using "sage -f PKG", should there be an analogous > command which uninstalls and then rebuilds the Makefile? Or should "make > PKG-clean" itself rebuild the Makefile?
The generated file `build/make/Makefile` is output by the `./configure` script. In fact, that's its main purpose. When switching branches in this case the best thing to do is to re-run `./configure`. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34Zdns1HXHzhYLGUg0TQbb3xXvK9%2BTV_bii1sBgWJfCW1Q%40mail.gmail.com.
