On 06/ 9/10 05:40 PM, William Stein wrote:
On Wed, Jun 9, 2010 at 9:11 AM, Dr. David Kirkby
<david.kir...@onetel.net> wrote:
On 06/ 9/10 12:40 PM, Dima Pasechnik wrote:
Well, I saw upgrades fail repeatedly, and William was writing here
that -upgrade is basically not ready
for prime time use.
Indeed, one needs to have at least an spkg dependencies mechanism in
place, before -upgrade
can be done in a fool-proof way. At the moment it is adhoc - an spkg
can be checking that another spkg is there and has version at least
something, but this is not supported in any consistent way, e.g. like
it is done with Debian packages.
I.e. there is no declarative facilities in place that would allow one
to specify such an interdependency,
they rather need to be hard-coded into the spkg install script.
So one needs to develop/adopt such a scheme, before -upgrade can be
made safe...
I've looked briefly at /local/bin/sage-update. Something that I think is
flawed is that if package B depends on A, and A is updated, B is not
recompiled.
Wrong.
The 'deps' file only lists the dependencies, but not version numbers.
Wrong.
Looking at spkg/standard/deps, I see:
$(INST)/$(FPLLL): $(BASE) $(INST)/$(MPIR) $(INST)/$(MPFR)
$(SAGE_SPKG) $(FPLLL) 2>&1
Let's assume MPIR gets updated. It would be wise to recompile fplll, even if
its not necessary to do so. Knowing when it is necessary and when it is not
necessary, would be hard to know.
Not true.
The variable $(MPFR) is set to mpfr-version_number.
The other issue is that spkg/sandard/deps sometimes has inferred
dependencies. For example, Pyton depends on zlib. PolyBoRi depends on Pyton.
But zlib is not listed as a dependancy of PolyBori, though it is inferred
via python.
What's wrong with that? I think make takes care of that automatically.
IMHO, if zlib is rebuilt, python should, and so polybori rebuilt. At the
moment, neither will happen if I've understood things correctly.
Perhaps you don't.
Obviously I don't.
It would be useful if a failed upgrade could be worked on, to try to get it
to work, rather then just say "It's failed, so I'll rebuild from scratch".
A failed upgrade can be worked on. I've had failed upgrades, and in
that case I fix them. Since I know Sage well, I can always fix them.
The point is not to just fix the upgrade - that only helps you on that one
occasion. But use the information gained by fixing it to improve the upgrade
process. Work out why it fails for some people some times.
William
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
