On 10/13/2009 08:36 PM, David Kirkby wrote:
> 2009/10/13 Ralf Hemmecke <r...@hemmecke.de>:
>> Would there be interest in the following workflow for installing sage.
>>
>> a) Get the sage tarball
>> b) extract the tarbal to SOMEDIR
>> c) cd SOMEDIR
>> d) configure (with or without --prefix)
>> e) make
>> f) make install
> 
> I would add
> g) make test

> I must admit, I would prefer this, as it tends to be more common.

Right.

 > But to write the configure.ac, which generates the Makefile, would be
> quite a bit of work to get it right.

Just generating the toplevel makefile (and perhaps sage-env) should be 
easy. But you probably also mean spkg/install and spkg/standard/deps. If 
these would be the only files (in a first round) that would be doable. 
Have I forgotten anything?

> Most, if not all of the pre-req-0.4 thing I wrote recently would no
> doubt then be moved to this top-level configure script if this was
> done.

What is pre-req-0.4?

Anyway, it seems there is no interest from other sage developers in such 
a change or is there? And if yes, what would be the dream?

Ralf

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to