> Could you post an example for a the files/configuration you use to
> create the srpm?
I'm not sure how familiar you are with RPM packaging, so please let me
know if I describe something that is unclear. My build directory
structure is as follows
~/src/rpm/BUILD --> this is tar xvf sage-version.tar is done; it's
the root of the build process
~/src/tmp/sage-version-buildroot --> this is where everything is
delivered to for RPM packaging; you can think of this as the / (top
level directory) when the RPM is unpackaged.
So, the build process equates to the following:
# The make process
1. cd ~/src/rpm/BUILD/sage-version/
2. make -j2
3. export PATH=~/src/rpm/BUILD/sage-version:$PATH
4. pushd devel/doc
5. make html
6. cd const
7. ./build_pdf
8. popd
# the make install process (continues from previous steps)
9. mkdir ~/src/tmp/sage-version-buildroot/usr/bin
10. ./sage -c 'install_scripts("~/src/tmp/sage-version-buildroot/usr/
bin")'
# Account for one of my trac tickets
11. mv ~/src/tmp/sage-version-buildroot/usr/bin/kash ~/src/tmp/sage-
version-buildroot/usr/bin/kash.sage
12. mv ~/src/tmp/sage-version-buildroot/usr/bin/M2 ~/src/tmp/sage-
version-buildroot/usr/bin/M2.sage
# typically, it's not desired to have to download files for RPM
packages, so I have a local copy of database_gap
13. cp ~/src/rpm/SOURCES/database_gap-4.1.10 ~/src/rpm/BUILD/sage-
version/
14. ./sage -i database_gap-4.1.10
# put the const documentation is the proper place
15. pushd devel/doc/const
16. mkdir -p ~/src/tmp/sage-version-buildroot/usr/share/doc/sage
17. cp const.pdf ~/src/tmp/sage-version-buildroot/usr/share/doc/sage
18. popd
# finally install everything into its RPM root dir
19. DESTDIR=~/src/tmp/sage-version-buildroot/usr/lib make install
# Account for my other tarc ticket
20. chmod 755 ~/src/tmp/sage-version-buildroot/usr/lib/sage/local/lib/
libhistory.so.*
21. chmod 755 ~/src/tmp/sage-version-buildroot/usr/lib/sage/local/lib/
libreadline.so.*
That is it in a nutshell. That leaves me with two concerns:
1. I believe the make install process will copy over everything
including the development/build files which are not really needed in
the final RPM. Can you please point out which directories contain
those files so that I can trim down the RPM size
2. the make process, and subsequently the make install, will create
libraries for ATLAS, BLAS, LAPACK, etc even though they are already
available on the build system in /usr/lib (for the libraries) and /usr/
include (for the headers). How can I modify the make process to detect
that those libraries are already on my system and NOT rebuild them?
This is probably the biggest optimization I could make.
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---
