Jeroen Demeyer wrote:
On 2014-04-17 16:57, John Cremona wrote:
In fact ot make sure that libraries linked to NTL gets rebuilt you
should
run "SAGE_UPGRADING=yes make".
But surely if the dependencies are correctly specified this should not
be necessary?
Unfortunately, that's not the case. Sage no longer makes a difference
between "upgrades" and normal builds, everything is considered a normal
build.
Perhaps we should consider making SAGE_UPGRADING=yes the default?
And/or stop touching files here in sage-spkg, since otherwise a later
'make' with SAGE_UPGRADING=yes won't work (as expected):
# Check whether the package is already installed. We do this before
# we download the package. We do a second check later, in case the
# user didn't supply a version number and we don't find a local
# matching package (case 3 above).
if [ $INFO -eq 0 -a $FORCE -eq 0 -a -f "$SAGE_SPKG_INST/$PKG_NAME" ]; then
echo "Package $PKG_NAME is already installed."
echo "Use 'sage -f $PKG_SRC' to force a reinstallation."
# Touch installed file such that "make" considers it up-to-date.
touch "$SAGE_SPKG_INST/$PKG_NAME"
exit 0
fi
Not sure whether it makes sense to add an option (to sage-spkg; 'make'
already has '-t', but I don't know whether that works from the
top-level) to touch the file regardless of whether it really got
rebuilt/reinstalled; one can of course always fake manually (although
that might get tedious for many, probably all dependent, packages).
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
