I think it would be good to keep the install script for Travis-CI as close as possible to what you would normally do to install a package in Sage, that is, create an updated tarball of your repository and copy it to upstream/, update the checksums and then install it with sage -i. This way, Sage will handle the details of running the spkg-install script. You can set a custom docker entrypoint to avoid running everything inside a Sage subshell, see for example here <https://github.com/mwageringel/fgb_sage/blob/b6924832fabe86f274e4e43b7271f0f6565a72a8/.travis.yml#L20>, though I used pip for installing the package.
-- 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/11a16baa-5537-4167-9f3d-796297c717d0%40googlegroups.com.
