#19549: Get rid of libtool archives (*.la)
-------------------------------+-------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.10
Component: build | Resolution:
Keywords: sd70 | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+-------------------------
Comment (by fbissey):
I am not sure what other answer you were expecting from me. Distros like
Gentoo (and most others I would think) get rid of them. The good question
is how to do it in sage? The easiest way would be for `sage-spkg` to do
the scanning. We don't want it to be done as an afterthought once the
`sage` build is finished.
The problem is that you don't have a staging phase before putting the file
in your tree. So you cannot `stage` then remove the ugly stuff and then
put it in your tree (or prefix if you will). Which means that essentially
you may have to scan the whole `$SAGE_LOCAL/lib` for `.la` file after you
have issued `make install` for every package. Could it be added to `sage-
spkg` to do once `spkg-install` proper is finished? How would that
interact with `spkg-check` is also something to think about because
building test may rely on these `.la` files.
--
Ticket URL: <http://trac.sagemath.org/ticket/19549#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 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/d/optout.