On Friday 17 January 2014 16:26:56 Erik Quaeghebeur wrote: > Hi, > > > For development on Sage (such as reviewing), is there a gentoo-specific > setup/approach best to follow? > > So, I'd like to know the Gentoo-specifics for > <http://www.sagemath.org/doc/developer/walk_through.html>. > Specifically, is it possible to set up a local/personal live ebuild that > points to the current local/personal branch of the sage source, so that > building allows me to test the changes? > > > Thanks, > > Erik
I think in that case you unmask and use the 9999 ebuilds that will fetch the
latest sources via git. These ebuilds inherit the git-2 eclass[1] that let you
override the repository, branch and commit via the
packagename_LIVE_REPO
packagename_LIVE_BRANCH
packagename_LIVE_COMMIT
environment variables; packagename should just be the ebuild name with hyphens
replaced by underscores: sage, sage_clib, sage_baselayout, sage_doc.
If you need to apply some additional patches, e.g. for gentoo specific
changes, use the epatch_user[2] functionality and put the patches under
/etc/portage/patches/sci-mathematics/<PF|P|PN>[:SLOT]/
e.g.
/etc/portage/patches/sci-mathematics/sage-9999/fix-directory.patch
(patch must end with ".patch"). This way you should not need to setup a new
overlay, maybe a little script that sets all environment variables will be
useful.
Cheers,
Christopher
[1] emerge eclass-manpages ; man git-2.eclass
[2] man eutils.eclass
signature.asc
Description: This is a digitally signed message part.
