Re: extfs: spaces in files names stored in archive file

[Pavel Roskin <proski gnu org>]

Hello!

> > $ /usr/local/share/mc/extfs/uzip list arch.zip
> > -rw-r--r--    1 500      500        445527 Feb 05 2002 20:34 Some name.jpg
>
> 1) Is it the same in case of soft links ?

I gave you that example so that you can find out yourself.  The uzip 
script is quite mature.  Make a zip archive and run uzip on it.  
Basically, extfs takes the output of "ls -al", so you can use it as well.

> -rw-r--r--    1 500      500        445527 Feb 05 2002 20:34 Some name.jpg ->
> another name.jpg

That's clearly a regular file.  Make a link and see the difference.

> 2) What to do with files with " -> " in their names ?

$ /usr/local/share/mc/extfs/uzip list arch.zip
-rw-r--r--    1 500      500        445527 Feb 05 2002 20:34 a -> b

Works for me.  Still extfs is not designed to understand all situations, 
just most of them.  You can still consuse it:

<proski portland ln>$ ln -sf "b -> c" a
<proski portland ln>$ ln -sf c "a -> b"
<proski portland ln>$ ls -al
total 1
drwxrwxr-x    2 proski   proski         96 Nov  5 08:44 .
drwxrwxr-x    6 proski   proski        144 Nov  5 08:43 ..
lrwxrwxrwx    1 proski   proski          6 Nov  5 08:44 a -> b -> c
lrwxrwxrwx    1 proski   proski          1 Nov  5 08:44 a -> b -> c

Now do "ls -al >list" and then "cd list#lslR" in mc to see what I mean.

extfs doesn't check the size of symlinks, but it checks the file type 
field in the permissions.  It can be improved if you really care.

> 3) How to test if output produced by the script is good ? [which lines are
> wrong]
> [I receive cryptic "could not parse" with NO additional info]

Add additional debug statements to the code or try to make "ls -al" 
produce exactly that line.

-- 
Regards,
Pavel Roskin