William Stein wrote:
> There's also a "make install" option, after you complete the build.
> You have to set the environment variable DESTDIR to the target directory,
> then type "make install". We needed this for the Debian package.
>
> It's not coupled so much. The only coupling is that the
On Saturday 17 March 2007 8:31 am, Mark wrote:
> > 1) Simple ebuild that just runs the sage build process and
> install
> > all of the sage stuff out of the way (/opt/sage). The
> difficult
> > step would be divorcing the build time location from the run
> time
> > location (b/c
There needs to be an error message for the two notebooks that saids
that the server is down for unknown reasons. I look stupid to people
who I have told to look at my stuff at sagenb.com. They probally think
that I gave them a wrong url.
On 3/17/07, William Stein <[EMAIL PROTECTED]> wrote:
>
> On
Hi list
I have done a similar effort for debian some time back (greater than 6
months). An alioth pkg-sage project
(http://alioth.debian.org/projects/pkg-sage/) was even set up to begin
a real attempt at packaging up sage for debian. Unfortunately, the
alioth build machine crashed and the small am
On 3/17/07, Robert Miller <[EMAIL PROTECTED]> wrote:
> Has anyone else been having trouble connecting to sage.math the past
> few days?
sage.math was fine last night. It went down sometime today. I don't
have physical
access to the machine, so there is nothing I can do about it.
Fortunately, a
On Mar 16, 2007, at 10:33 PM, Mike Hansen wrote:
>
> Hello,
> I'm running some computations in SAGE for my research, and they are
> quite time consuming, but proudly parallel. I'd obviously like to use
> DSAGE to speed them up, but I have a few questions.
Hi Mike,
I am glad you are making use o
Quote:
**
> 1) Simple ebuild that just runs the sage build process and
install
> all of the sage stuff out of the way (/opt/sage). The
difficult
> step would be divorcing the build time location from the r