On Thu, 25 Jan 2007 00:03:02 -0800, Robert Miller <[EMAIL PROTECTED]> wrote:
>
> Awesome. Not only is my confusion cleared, but the option that was
> causing it no longer exists...
Yep. This confused everybody! The code to do it is still in the
script SAGE_ROOT/local/bin/sage-sage, but it's
Awesome. Not only is my confusion cleared, but the option that was
causing it no longer exists...
On Jan 24, 11:45 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> I think it's a distinction between packages (optional or otherwise)
> and the core sage library (found in devel/sage/...). The latter
I think it's a distinction between packages (optional or otherwise)
and the core sage library (found in devel/sage/...). The latter is
under the repository and you can have many branches ("clones")
whereas the former is not.
- Robert
On Jan 24, 2007, at 11:39 PM, Robert Miller wrote:
> Ok
A relevant conversation with William, earlier:
William wrote:
>> By the way, what are the differences between the following?
>>
>> sage -update
>
>This is the first step of doing "sage -upgrade". It downloads new
>packages but doesn't apply them. It confuses WAY more people (at least 3)
>than i
"sage -update" is not supported in 1.8.2.1 which is out. I got it
confused with upgrade.
On 1/24/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>
> So I guess -update followed by -update-build /should/ be the same as -
> upgrade then. Let me know if that works.
>
> On Jan 24, 2007, at 11:31 PM, a
Ok, I think I know a little more about what went wrong:
After doing sage -update-build, sage compiles just fine. My assumption
was that
sage -update
sage -br
would do the trick, but it seems as if sage -br doesn't build the
downloaded updates... I'm wondering, what does sage -br actually do?
Wh
So I guess -update followed by -update-build /should/ be the same as -
upgrade then. Let me know if that works.
On Jan 24, 2007, at 11:31 PM, alex clemesha wrote:
> if you type 'sage -advanced' you get an explanation
> of all possible flags:
>
> (at the bottom:)
>
> -update -- download la
if you type 'sage -advanced' you get an explanation
of all possible flags:
(at the bottom:)
-update -- download latest non-optional SAGE packages (do not build
them)
-update-build -- build and install all downloaded non-optional SAGE
packages
-upgrade -- download, build and install
Ok, I got it mixed up, what I did was -update followed by -br. Point
is, after update, my sage fails to build.
On Jan 24, 11:27 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> Yeah, upgrade != update (though to be honest I don't know the
> intricacies of the differences).
>
> On Jan 24, 2007, at
Yeah, upgrade != update (though to be honest I don't know the
intricacies of the differences).
On Jan 24, 2007, at 11:26 PM, Robert Miller wrote:
> Look carefully at my previous post: all I did was sage -upgrade
> followed by sage -br.
>
> On Jan 24, 11:23 pm, Robert Bradshaw <[EMAIL PROTECTED
Look carefully at my previous post: all I did was sage -upgrade
followed by sage -br.
On Jan 24, 11:23 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> Doesn't look like it got the new sagex package, have you tried sage -
> upgrade?
>
> On Jan 24, 2007, at 11:14 PM, Robert Miller wrote:
>
> > Thi
Doesn't look like it got the new sagex package, have you tried sage -
upgrade?
On Jan 24, 2007, at 11:14 PM, Robert Miller wrote:
> This only emphasizes my frustration with mercurial:
>
> robert-millers-powerbook-g4-12:/Volumes/DATA/sage-1.7 robert$ sage
> -update
> Using SAGE Server http://sag
This only emphasizes my frustration with mercurial:
robert-millers-powerbook-g4-12:/Volumes/DATA/sage-1.7 robert$ sage
-update
Using SAGE Server http://sage.math.washington.edu/sage//packages
http://sage.math.washington.edu/sage//packages/install --> install
[.]
http://sage.math.washington.edu/sa
You have an old old version of sagex, which is before Robert Bradshaw
added support for "+=" (etc.). You must do
sage -upgrade
not just hg_sage.pull(), which only gets the Python/SageX library code.
In particular, Nick's guess is exactly right:
On Wed, 24 Jan 2007 19:23:58 -0800, Nick Ale
Just a guess, but I believe that in place update (+=, *=) were just
added to sagex. You might try updating that package.
Nick
Robert Miller wrote:
> Getting the following error when building the latest version of SAGE:
>
> robert-millers-powerbook-g4-12:/Volumes/DATA/sage-1.7 robert$ sage -br
>
15 matches
Mail list logo
