On Sun, 04 Mar 2012 17:51:47 Michael Orlitzky wrote: > On 03/04/2012 01:15 AM, François Bissey wrote: > > That's a bit more complicated than that. But in essence yes you can. > > Now do you know how to get your version of the library to be used > > instead of the system one? Getting a copy and recompiling it is just.... > > hum..... 2/3 of the story (just so you know I have a fairly good idea > > about > > that last bit). > > > >> 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? > > > > I think you are missing the point. Sage has tools to enable you to only > > rebuild a minimal subset of files - it is disabled in sage-on-gentoo - > > that enables to test a small change relatively quickly. If I want to do > > the > > same with s-o-g I have to rebuild the whole thing. > > If the sage library comes with a makefile (akin to sage -b now), can't I > just do make && make install DESTDIR=/path/to/sage? It's not a big deal > to overwrite $PREFIX/usr/whatever/sage/...
this is python, you would want to get familliar with setup.py. I think it is a great deal to overwrite the content of your prefix system. First, all promises about safe upgrades without any (dangerous) left overs are off! That's my top concern. You modify files that are under package manager control, potentially adding or removing some.... you can deal with the mess. Francois -- 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
