[Openmcl-devel] Lisp image filename.
Chun Tian (binghe)
binghe.lisp at gmail.com
Tue Oct 7 07:52:16 PDT 2008
> On Mon, 6 Oct 2008, David Brown wrote:
>> Is there any particular reason for the distinction on darwin of
>> the image by tacking an ".image" onto the filename, and other
>> platforms that use an equivalent named file in uppercase?
> Lack of foresight, mostly. Inertia factors into it, too: there are a
> handful (maybe a few handfuls ...) of places in the code and
> documentation that "know" that some platforms use the case-inversion
> convention and others use ".image". There have always been exceptions
> to assumptions about a platform's case-sensitivity (it's usually an
> attribute of the filesystem, not of the OS), and those exceptions are
> likely to get more common. Using the ".image" convention on all
> platforms (as you propose) makes sense and I agree that it's worth
> doing, but the change will probably be at least a little disruptive.
> (Not so disruptive that it shouldn't be done, but at least a little
I also suggest this change (using .image convention on all platforms).
Now It's impossible to checkout CCL repository (non-Mac platform) on
Mac OS X, just because svn cannot distinguish the two files with the
same name but different case.
I'm running a Solaris 10 virtual machine on Mac OS X by VMware Fusion,
and mapping HFS directories into Solaris. I want to checkout CCL for
Solaris on Mac and then use it in Solaris, but cannot do (the reason
above). Another side, install a svn client on Solaris 10 is quite
hard, so many sunfreeware packages to install, and it could be avoid
if CCL's svn file-case issue is gone...
More information about the Openmcl-devel