On 2014-08-04 15:17, William A Stein wrote:
Hi,
I installed Sage-6.3.beta6 on SageMathCloud, then installed a big list
of optional packages, including cryptominisat. I was surprised when
the next day a user reported that CryptoMiniSat didn't work, and when
you attempt to use it, you see
Run "install_package('cryptominisat')" to install it.
I tried the above (as the owner of the sage install), and it did not
fix the problem. What did fix the problem was typing "sage -b".
So... it seems like somebody removed doing "sage -b" after installing
optional packages from the build system (if it was ever there?).
Running "sage -b" after installing packages has always been needed,
nobody removed anything.
I don't consider that a bug, it's consistent with: whenever you change
something to your Sage setup, run "sage -b" or even better "make".
I would not be in favour of automatically running "sage -b" since you
might want to install several packages but run "sage -b" only once, you
might want to do something else like checking out some git branch (after
which you need to do "sage -b" anyway) and it wouldn't work for standard
packages as you said. I would also advice against doing "sage -b" while
Sage is running, so the install_package() Sage command couldn't do it.
--
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.
