On Jun 29, 2010, at 10:41 AM, kcrisman wrote:
>>> So I made another folder to put it in, copied it there. The same
>>> thing happened, even though that folder was otherwise empty - message
>>> "You can’t copy “Sage” because it has the same name as another item on
>>> the destination volume, and that volume doesn’t distinguish between
>>> upper- and lowercase letters in filenames"
>>> so I'm not sure what to do next. Weirdly, it copied a lot - about
>>> half - maybe through /local/bin but quit in the middle of that, and
>>> did not copy the actual ./sage script.
>>
>> Very odd indeed. I use case-sensitive HFS which is not the default. It has
>> caused me some problems in the past e.g. with Steam. It looks like this is
>> probably the reverse problem happening. There must be two files somewhere
>> that differ only by case--that seems like a very bad thing. I can't
>> remember if I did a clean before the build, so there may be some cruft in
>> the package causing the problem.
>
> I've had this problem copying regular Sage at times too... not
> reliably, but Singular vs. singular I think may have been the problem
> at the time. In fact, since the files in local/bin seem to have
> copied in alphabetical order, and the last three files copied seem to
> have been Singular, Singular-3-1-0, and TSingular (this last being out
> of order for some reason, but no others I can tell), I wouldn't be
> surprised if that were causing the trouble again.
singular seems to be the culprit here as well:
: Sage.app : 0; find . | tr 'A-Z' 'a-z' | sort | uniq -d
./contents/resources/sage/local/bin/singular
: Sage.app : 0; md5 Contents/Resources/sage/local/bin/singular
MD5 (Contents/Resources/sage/local/bin/singular) =
b103365ac3178e9938593b06a9cf727e
: Sage.app : 0; md5 Contents/Resources/sage/local/bin/Singular
MD5 (Contents/Resources/sage/local/bin/Singular) =
b103365ac3178e9938593b06a9cf727e
So Singular and singular are the same file. At least it's not as bad as if
they were different files, but it's a bad thing IMHO. It means that a binary
distribution built on a case sensitive filesystem won't work on a case
insensitive file system (because of the copying problems you saw).
In singular-3.1.0.4.p6/spkg-install I found:
# Lower case version is convenient.
$CP -f Singular singular
which seems to indicate that we create the link for "convenience". I'm not
sure what that means. Is it ever called as singular anywhere? If so, then a
binary distribution built on a case insensitive file system won't work on a
case sensitive one.
Trac #1635 seems related, and what I see in spkg-install seems broken since it
keys off of Darwin rather than case-sensitivity of the file system, but I
haven't noticed any breakage from this (sage --singular starts at least). I'm
not sure what I would have to do to see it though.
I *HATE* case insensitive file systems.
Based on these two it appears that I cannot create a sage binary distribution
that will work for most OS X users. Well I guess I could build on a
case-insensitive disk image...
It seems to me that we should at least mention that if you use a case sensitive
file system on OS X you will have to build from scratch. Or we could provide
yet another set of dmg's Either is less than optimal obviously. Any thoughts?
Obviously we'll have to deal with this sort of thing as we move to Windows.
In fact I can't even tell if NTFS is case sensitive or not based on:
http://support.microsoft.com/kb/100108
Do we have any policies on stuff like this?
-Ivan
--
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
