> That's expected.  The package build directory is under SAGE_LOCAL 
> ($SAGE_LOCAL/var/tmp/sage/build/gap-4.10.0.p0) but the file's 
> destination path ($SAGE_LOCAL) is appended to this.  This is how it's 
> supposed to work (DESTDIR installation). 
> It's probably too late to diagnose now (though it would be good if you 
> could give steps to reproduce). 

Yeah, unfortunately my main goal was getting a working Sage install, so the 
evidence has been eliminated, so to speak.

>  But the question is what type of file 
> was 
> /Users/karl.crisman/Downloads/sage/local/./share/gap/bin/x86_64-apple-darwin15.6.0-default64/src
> that it refuses to overwrite because it was supposedly a directory? 

I can tell you a rough answer to that, after my most recent upgrade the 
name of the directory seems to have changed slightly though:

$ ls -l 

total 32

lrwxr-xr-x  1 karl.crisman  78570554  18 Aug 14 14:39 config.h -> 

lrwxr-xr-x  1 karl.crisman  78570554   9 Aug 14 14:39 gac -> ../../gac

lrwxr-xr-x  1 karl.crisman  78570554   9 Aug 14 14:39 gap -> ../../gap

lrwxr-xr-x  1 karl.crisman  78570554   9 Aug 14 14:40 src -> ../../src

> The GAP package installs a *symlink* at the path 
> $SAGE_LOCAL/share/gap/bin/<platform-triplet>/src 
So yes, that is what seems to be happening.

> When you upgrade GAP, first of all, it should be *uninstalling* the 
> previous gap package, so this link should just be removed.  The 
> question is was it a symlink for you in the first place?


>  Or an actual 
> directory?  When you run `make clean-gap` does it get removed? 
Is that something I can do from within Sage?  I didn't know that was a make 
target for us.   My assumption is that the symlink was not removed or it 
wouldn't have complained.

You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Reply via email to