That makes more sense, if you call from within A's sage-env the makefile of B then you'll have a bunch of environment variables set pointing to A.
On Monday, May 19, 2014 3:40:01 PM UTC+1, Ralf Stephan wrote: > > I *think* what happens is that 'make' gets called as subprocess from > patchbot (the A python), > and the call inside spkg-install (of B spkgs) somehow gets it wrong and > installs the packages > into A. logs can be found at > https://github.com/robertwb/sage-patchbot/issues/35 > > > On Mon, May 19, 2014 at 4:33 PM, Ralf Stephan <[email protected]<javascript:> > > wrote: > >> >> On Mon, May 19, 2014 at 4:25 PM, Volker Braun >> <[email protected]<javascript:> >> > wrote: >> >> Not sure if I understand, but "git clone /path/to/A B" would create B as >>> a completely independent source tree. >>> >> >> ...which installs back python and its packages into A. And for me as >> python newb this >> doesn't look right. But what do I know? >> > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
