The Sage 6.9.rc0 release brings an important change for developers
(including reviewers) of Sage packages. It applies to all new-style
packages.
**Whenever you change any package metadata, you need to run ./configure
for your changes to be applied**
Package metadata means:
* the list of packages
* version of a package
* type of a package
* dependencies of a package
* environment variables influencing packages: SAGE_MP_LIBRARY,
SAGE_INSTALL_GCC, SAGE_INSTALL_CCACHE, SAGE_PYTHON3
It used to be that running any kind of "make" or "sage -i" command
automatically ran "./configure", but that quickly became annoying (see
Simon King's post about "sage -i")
Since configure depends on the Sage version, changing Sage versions will
cause configure to be run again. So, if package metadata changes because
of a Sage upgrade, there are no manual steps needed.
The section on making packages in the developer's guide also got updated
with all the recent changes regarding packages.
Jeroen.
--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
