[Gnu-arch-users] Re: arch on windows?

[John Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I just did a check on the MAC here in the office. And when using
Journaled HFS+, I made a path with > 900 characters and had no problems.
When I went > ~1000 the shell started complaining that getcwd "Cannot
access parent directories: Result too large".
So my guess is that either bash or the filesystem doesn't support > 1024
characters. This is a heck of a lot better than 256, so we may not have
problems under Mac, and maybe the only thing that needs patching is the
Win32 port.
There might be issues with a different filesystem (HFS, IIRC Mac can use
UFS, etc) But at least HFS+ seems okay.

So if all we do is switch from {arch}/c/c--b/c--b--v/c--b--v--p-nn.* to
{arch}/c/--b/--v/--p-nn.* (I'm leaving in the -- because 'b' can be
empty) we'll probably have a 75% solution. It would be nice if tla
anywhere could understand this format, but the alternative could be tla
"make-tarball" which just reverts everything under {arch}.
At least on win32, there is also the 8.3 hack, which scales slightly better.

We still have the problem of exporting archives. As Ron mentioned Apache
& IIS won't serve a long filename. If we change archives to the same
c/--b/--v layout, that makes it easier, but it breaks a lot of
compatibility. But any solution here *has* to be in tla-mainline for it
to be useful. You could just export your archive to other win32 clients,
but that doesn't seem very nice.

John
=:->

PS> At least some of the other 25% is to make "tla commit" not create
the directory ,,commit-c--b--v--p-nn.* where * is also very long. "tla
get" is also bad, but at least you can say "tla get c--b shrtnam" and it
will use the short name.

Ron Parker wrote:

| On Mon, 12 Jul 2004 09:21:36 -0500, John Meinel <address@hidden>
wrote:
|
|
|>I just wanted to mention that Ron is also hoping to have tla run under
|>MacOSX, which afaik has the same problem with long pathnames, but
|>doesn't have a legacy 8.3 mode, or a long path API. I'm not positive on
|>this, I'm just repeating what I remember from him.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA8uOMJdeBCYSNAAMRAk+iAKCgAiatwLb1lasiNCUh+CS8GHIRrACeMR4T
JRwz2HFPpFEyVqDztIKc92U=
=a1F3
-----END PGP SIGNATURE-----