Re: [gentoo-science] Making ebuilds for sage packages

[Christopher Schwan <cschwan@students.uni-mainz.de>]

On Sunday 02 December 2012 17:12:37 you wrote:
> Hi,
> 
> I'm trying to make an ebuild that installes this here into my
> sage-on-gentoo installation:
> https://bitbucket.org/matroid/sage_matroids
> 
> Their setup.py does the following:
> 
> if not os.environ.has_key('SAGE_ROOT'):
>     print "    ERROR: The environment variable SAGE_ROOT must be defined."
>     sys.exit(1)
> else:
>     SAGE_ROOT  = os.environ['SAGE_ROOT']
>     SAGE_LOCAL = SAGE_ROOT + '/local'
>     SAGE_DEVEL = SAGE_ROOT + '/devel'
>     SAGE_INC   = SAGE_LOCAL + '/include/'
> 
> and I wonder if this is wrong?  Is SAGE_LOCAL="/usr" on Gentoo?  In
> particular, where should python packages go that were installed by such
> an ebuild? Maybe into /usr/lib/python/site-packages ?
> 
> Cheers,
> Thomas

For sage-on-gentoo it is wrong, because here SAGE_LOCAL != SAGE_ROOT/local. In 
particular, we have

		SAGE_ROOT="${EPREFIX}/usr/share/sage"
		SAGE_LOCAL="${EPREFIX}/usr/"
		SAGE_DATA="${EPREFIX}/usr/share/sage"
		SAGE_SHARE="${EPREFIX}/usr/share/sage"
		SAGE_DOC="${EPREFIX}/usr/share/sage/devel/sage/doc"
		SAGE_EXTCODE="${EPREFIX}/usr/share/sage/ext"

(from sage-4.5.1-r1.ebuild). Python packages should be installed to the 
default location, just use python/distutils eclasses for that.

Cheers,
Christopher