Re: [Gnu-arch-users] Re: tla1.2 on cygwin

[Dustin Sallings]

On Mar 5, 2004, at 21:44, Tom Lord wrote:

> I don't understand what the subdir structure has to do with case
> sensitivity.   Can you explain?

	http://bsdboy.west.spy.net/cgi-bin/viewarch.cgi/address@hidden 
-2004s/ViewARCH--devo--0.0.8--patch-21/%7Barch%7D

        There are three categories people have called this project:

        ViewARCH
        ViewArch
        viewarch

	When I check that out, only the first one is created, and all of the  
stuff goes into the first one.  I had at one point checked out a tree  
similar to this where I use a different category name than the one that  
got chosen.  I managed to commit a patch at one point, but now if I try  
to check out the tree on a NetBSD box, I get this:

Error calling `vu_lstat' for  
"/tmp/,,get.vap22.1078551330.13089.1/,,next-patch.1078551332.13089.40/ 
new-files-archive/./{arch}/viewarch/viewarch--py22/viewarch--py22- 
-0.0.7/address@hidden/patch-log/patch-1" (No such file or  
directory)PANIC: I/O error

	The short story is that the names would be completely irrelevant if  
they were confined within the namespace of the ``global'' archive name.  
 I.e., it'd be my fault if I used two conflicting category names in the  
same archive if I had to deal with the limitation of working with  
case-insensitive filesystems.

> _If_ you are correct that case issues effect many (I've only ever
> heard you complain) -- there are sane ways to handle that (i.e., with
> a VU namespace handler).

	Well, I think restructuring is sane, but I do understand the need to  
maintain compatibility.  In my previous messages, I listed it as what I  
felt was the ideal solution since I think it makes the whole thing make  
more sense (I still don't understand why you wouldn't want the highest  
level to be the archive name like it is everywhere else).  I don't  
assume to know every solution, or even the most practical solution.

> How do you cope with #include, btw?   And, what does tar do?

	I'm not sure what you mean by #include.  I haven't seen any problems  
related to that.  Tar works just fine.  The filesystem preserves case  
just fine, it just ignores it when accessing files or directories.

--
SPY                      My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <address@hidden>
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________