rebase numpy 1.5.1 on latest version in the main tree

Package-Manager: portage-2.2.0_alpha142
revbump to correct the definition of GAP_STAMP in the variables patch.

Package-Manager: portage-2.2.0_alpha144
Getting an ebuild for numpy-1.7.0b2

Package-Manager: portage-2.2.0_alpha144
masking numpy-1.7.0_beta2
Massive update: use cython 0.17.2 (use upstream patch), lock matplotlib to 1.1.x (major breaks with 1.2.x) - allow the use of numpy
1.7.0beta2

Package-Manager: portage-2.2.0_alpha144
remove old

Package-Manager: portage-2.2.0_alpha144
reverting the masking as it makes repoman unhappy. dep properly enforced in sage ebuild.
removing cython from the overlay - now using cython 0.17.2 from main tree.
remove distutils_src_configure from sage - it doesn't exist :)

Package-Manager: portage-2.2.0_alpha144
Initial ebuild for sage-matroids. Requested by Thomas Kahle. It illustrate what to do to get an external module to build. It was an
interesting exercise.

Package-Manager: portage-2.2.0_alpha144
Install sage-matroids source along the standard sage sources making it testable in the process.

Package-Manager: portage-2.2.0_alpha144
try to deal with collision

Package-Manager: portage-2.2.0_alpha144
install in the right place?

Package-Manager: portage-2.2.0_alpha144
Finally put sage-matroids devel files in the right spot

Package-Manager: portage-2.2.0_alpha144
remove the numpy 1.7 patch as it turns out it is unneeded

Package-Manager: portage-2.2.0_alpha144
dev-python/numpy-1.5.1: add another patch from upstream

This should fix #445286 on bgo

Package-Manager: portage-2.2.0_alpha144
Manifest-Sign-Key:
Merge pull request #175 from xhub/master

dev-python/numpy: add another patch from upstream
Patch sage/all.py to allow matroids to be imported if they are installed.

Package-Manager: portage-2.2.0_alpha144
5.5rc0: baselayout

Package-Manager: portage-2.2.0_alpha144
5.5rc0: add sage-run-cython

Package-Manager: portage-2.2.0_alpha144