#9761: Adjust spkg/standard/deps to build Python before zn_poly
-----------------------+----------------------------------------------------
   Reporter:  mpatel   |       Owner:  GeorgSWeber
       Type:  defect   |      Status:  new        
   Priority:  blocker  |   Milestone:  sage-4.5.3 
  Component:  build    |    Keywords:             
     Author:           |    Upstream:  N/A        
   Reviewer:           |      Merged:             
Work_issues:           |  
-----------------------+----------------------------------------------------

Comment(by leif):

 Is this documented in zn_poly's {{{SPKG.txt}}}?

 If zn_poly('s build system) depends on Python, {{{spkg/standard/deps}}}
 should of course reflect this; we could in addition ensure in its {{{spkg-
 install}}} that the current Sage's Python is already available; but see
 below (w.r.t. ''Sage's'').

 I though don't like making packages depend on Python just because some
 developers appear to be unable or unwilling to write shell scripts
 instead; the Fortran spkg here is IMHO an especially odd example, since on
 most systems it's a dummy package, but other packages have to wait until
 Sage's Python is ready to actually do nothing. (I would completely drop it
 from the standard distribution; shipping binary executables - in a
 ''source'' tarball! - isn't nice either.)

 Btw, William's Fortran problem on bsd.math was (also) due to a ''broken''
 Python installation/misconfigured environment.

 The long-term solution to such should be to ''generate'' the Makefile
 (including deps) in/after Sage's configure. Then we could omit some
 dependencies (e.g. because a system-wide Python is usable, too), drop [the
 build of] spkgs like Cephes completely on all systems but Cygwin, and
 remove ugly things like {{{$PIPESTATUS}}}.
 So we should take care not to make changes to lots of spkgs we would later
 have to revert/change, e.g. checking for {{{$SAGE_LOCAL/bin/python}}}; we
 could use properly set environment variables instead.

 Also, {{{spkg/standard/deps}}} (or a file it is generated from, which I'd
 prefer) should be under revision control.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9761#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to