#15615: Put ATLAS archdef tarballs into patches/ARCHS and resync ATLAS-lib dir
-------------------------------------+-------------------------------------
Reporter: jpflori | Owner:
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-6.1
Component: packages: | Resolution:
standard | Merged in:
Keywords: atlas spkg | Reviewers:
archdef cygwin | Work issues:
Authors: Jean-Pierre Flori | Commit:
Report Upstream: N/A | 1154b0d4c1f157d12f0e31cc883edf79531fdb3e
Branch: | Stopgaps:
u/jpflori/ticket/15615 |
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by jpflori):
Replying to [comment:3 vbraun]:
> Since we have to make our own ATLAS tarball anyways to embed lapack, I
would be in favor of putting the archdef tarballs in there as well. Even
though they are small, they are still binary stuff that we should keep out
of the repo if possible.
Yes, we also have to generate the autotools project an d put it in.
I'm not so found of not tracking and putting the archdefs tarballs into
the ATLAS tarball as there is no easy way to generate them as for the
autotools project, or getting them somewhere upstream as for the lapack
tarball.
--
Ticket URL: <http://trac.sagemath.org/ticket/15615#comment:5>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
