[SciPy-user] bdist_rpm build error in scipy_core from CVS
Fernando Perez
Fernando.Perez at colorado.edu
Fri Jan 28 19:54:12 EST 2005
Stephen Walton wrote:
> Now on to Fernando's helpful set of scripts :-). Kudos on these
> significant steps towards simplification of the scipy build and install
> process.
The other part of my setup (besides automated kickstart install building,
which I won't discuss for now; ask me if interested) is how to quickly build
RPMs out of the binary ATLAS tarballs which Pearu nicely compiles for us at
scipy.org. This is accomplished with the attached code.
Instructions:
1. Simply put all of this somewhere in your filesystem.
2. Make a src/ subdir there and put in src/ the ATLAS tarballs you want to
make RPMs for from
http://www.scipy.org/download/atlasbinaries/linux
These should be the uncompressed, untouched .tgz files you download. Don't
modify them in any way. Note that it is CRITICAL for this to work that they
are named
atlas<VERSION>_Linux_<ARCH>.tgz
ARCH is the string which the scripts and configs in my other email all refer
to, and which allow you to handle multiple architectures and YUM in harmony
(via the $YUM<N> variables, ARCH is stored as $YUM1).
3. Copy the COPYRIGHT notice to src/, so each RPM gets built with the right
notice. This is to comply with the copyright requirements of ATLAS
4. Read the top-level docstring for make.py, it explains the running, which is
trivial.
This will give you rpms which you can then drop in your architecture-specific
yum repositories (yum${RELEASEVER}-arch/${ARCH}), and you can then handle with
the same config multiple machines with different architectures cleanly.
I don't claim this to be perfect, but it works for me. If it breaks badly,
you either get to keep all the pieces, or you can send me the _fixed_ version :)
Regards,
f
ps. If this works for people, I'd like to ask Pearu to keep his current
naming conventions for the future. It would be nice if we could keep these
scripts in use for the long run without having to tweak them too much.
Changning ATLAS version numbers is trivial (one variable), but mucking with
the naming structure would require fiddling with the code.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: make.py
Type: application/x-python
Size: 4363 bytes
Desc: not available
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20050128/f70e1d97/attachment.bin>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: atlas-base.spec
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20050128/f70e1d97/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: COPYRIGHT
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20050128/f70e1d97/attachment-0001.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rpmmacros
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20050128/f70e1d97/attachment-0002.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rpmrc
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20050128/f70e1d97/attachment-0003.ksh>
More information about the SciPy-User
mailing list