#9761: Adjust spkg/standard/deps to build Python before zn_poly, and make two
other dependencies explicit
------------------------------+---------------------------------------------
Reporter: mpatel | Owner: GeorgSWeber
Type: defect | Status: positive_review
Priority: blocker | Milestone: sage-4.5.3
Component: build | Keywords:
Author: David Kirkby | Upstream: N/A
Reviewer: Leif Leonhardy | Merged:
Work_issues: |
------------------------------+---------------------------------------------
Comment(by drkirkby):
Replying to [comment:17 leif]:
> Replying to [comment:13 mpatel]:
> > Just to check on #9464: Are we generally going to be explicit about
all dependencies or just potential sources of confusion?
>
> I'd say making direct dependencies explicit is not a bad idea.
I've just thought of a reason why it is a good idea to be explicit about
all dependencies. Whilst before I was ''sitting on the fence'' over this,
I now believe there are advantages in listing every dependency directly,
for the reasons stated below.
I wanted to start a build of Sage, without building ATLAS, so I copied the
ATLAS libraries & headers from a previous Sage build, into a directory and
touched {{{spkg/installed/atlas-3.8.3.p14.}}} Now, when I start to build
Sage, neither Fortran, lapack or python are built.
But something that required Fortran, lapack or Python, but only listed
ATLAS as a dependency, could then fail to build.
Like it or not, people do sometimes copy parts of one build to another, in
order to save time. (Especially with ATLAS). That is more risky if
{{{spkg/standard/deps}}} does not explicitly list each and every
dependency.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9761#comment:23>
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.
