A while ago I posted in this forum with a problem regarding my efforts on creating an SRPM. At the time, I was told that even though there was no such entity, there was some work being done on a DEB package and that I should definitely continue my efforts.
Well, I am pretty close to the finishing it off (if anyone would like to see it, please let me know). In the mean time, I was wondering if I could clean it up a bit. One thing that I noticed is that the standard "make" process builds everything under the sun (that's why the distributable sage-version.tar file is so large). Well, as it turns out, over the course of time, I had already created standalone SRPMs for lapack, blas, atlas, etc - the list goes on. So, I was wondering what kind of changes would I have to do to my make process in order for SAGE to detect my existing installations of those libraries? Thanks in advance, Paul. P.S. I noticed that the "make install" is still experimental. There are a couple of things that I would recommend changing there. How do i go about submitting those comments? --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
