Details | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
6725 | siemargl | 1 | Acorn-specific usage instructions |
2 | --------------------------------- |
||
3 | |||
4 | As zipfiles can come from a variety of sources apart from Acorn machines, |
||
5 | consideration had to be given to the handling of dot-extensions, e.g. |
||
6 | "DOSFILE.TXT", "unix-filename.tar.gz". These are extracted as "DOSFILE/TXT" |
||
7 | and "unix-filename/tar/gz"; their names may or may not be truncated, |
||
8 | depending on where the files are being created: what filing system and, for |
||
9 | Filecore-based filing systems such as ADFS or an IDEFS or SCSIFS, which |
||
10 | disk/partition format (names will not be truncated if you're using E+ or F+). |
||
11 | |||
12 | Where truncation occurs, you must be REALLY careful about extracting files |
||
13 | from archives. The files |
||
14 | |||
15 | dummy_source.c and dummy_source.h |
||
16 | |||
17 | will both be extracted as |
||
18 | |||
19 | dummy_sour |
||
20 | |||
21 | UnZip will prompt you for confirmation of the over-writing of these files, |
||
22 | but you must be really careful unless you wish to lose files! Also, because |
||
23 | UnZip is a unix-ported program, the filenames are CASE SENSITIVE. |
||
24 | |||
25 | *unzip new/zip newfile |
||
26 | |||
27 | will extract 'newfile', but not 'NewFile', 'NEWFILE' or any other |
||
28 | combinations. However, you can use the -C option to force operations to |
||
29 | disregard the case of filenames. |
||
30 | |||
31 | The Acorn UnZip port has an additional feature to cope with the extraction of |
||
32 | files containing 'c' code. As you may be aware, Acorn Desktop C requires all |
||
33 | files called "foo.c" to be renamed to "c.foo", ie "foo" in a directory called |
||
34 | "c". |
||
35 | |||
36 | There are two ways of using this feature. |
||
37 | |||
38 | - The old way: use a colon-separated environment variable named "Unzip$Exts". |
||
39 | |||
40 | Any extensions found in this variable will be extracted to directories |
||
41 | named after the extension, with the extension stripped. For example: |
||
42 | |||
43 | *Set Unzip$Exts "c:h:o:s" |
||
44 | *unzip foo/zip |
||
45 | |||
46 | - The new way: use the -/ option. For example: |
||
47 | |||
48 | Any extensions found in the parameter for this option will be extracted to |
||
49 | directories named after the extension, with the extension stripped. For |
||
50 | example: |
||
51 | |||
52 | *unzip -/c:h:o:s foo/zip |
||
53 | |||
54 | If foo/zip contains a file named "foo.c", this file will be written as "foo" |
||
55 | in directory "c". This can be used to include "c:h:o:s:txt" to pull all the |
||
56 | text files out to a separate directory. |
||
57 | |||
58 | UnZip fully supports SparkFS Extra Field. This means that zipfiles created |
||
59 | with SparkFS or Zip (on RISC OS) will be correctly unzipped, including |
||
60 | filetypes. |
||
61 | |||
62 | UnZipSFX can be used to create self-extracting archives. To use it, just |
||
63 | create a common zipfile using Zip (or SparkFS), then load the UnZipSFX |
||
64 | executable into an editor (eg. Edit, Zap), go with the caret the end of the |
||
65 | file (using CTRL-CursorDown) and drag the zipfile to the editor window (in |
||
66 | other words, append the zipfile to the UnZipSFX executable). Now, saving the |
||
67 | resulting file (with filetype Absolute (&FF8)), you have a self-extracting |
||
68 | archive (ie. double-clicking on it will unzip the contents of the original |
||
69 | zipfile to the currently selected directory). |