On 03/03/2012 07:50 PM, François Bissey wrote:
On Sat, 03 Mar 2012 15:50:06 Michael Orlitzky wrote:
I think Francois was referring to how easy it is to hack on the
dependencies. Right now, you just extract the spkg, modify it, tar it
up, and sage -f it.
In prefix, you would revbump (-r1) your ebuild, stick a patch in the
'files' directory, edit the ebuild to use the patch, and then re-emerge
that package. If you don't like patches, you could also just set SRC_URI
to e.g. file:///my-modified-package.tar.bz2 and re-emerge.
No, I was refering to the ability to clone the sage hg repository and switch
to your own "homebrew" version of sage by running "sage -b". That isn't
supported right now in Gentoo (although I have idea on how to achieve it
I haven't done the perspiration yet to make it happen).
The best you can do with sage-on-gentoo is an equivalent of "sage -ba"
which will rebuild your own install in full . And you cannot switch between
clone of the tree.
If all of the dependencies were installed as pseudo-system prefix
packages, couldn't you just make a copy of the sage library, and type
'make' or whatever?
I guess my question is, if I want to modify some other program on my
system, I extract a copy in ~/src, modify what I want to, and then do
./configure && make. Why would the sage library be special?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
