Debian Codegraph @

macos/source/VolWarn.h

raw
1 /*
2 Copyright (c) 1990-1999 Info-ZIP. All rights reserved.
3
4 See the accompanying file LICENSE, version 1999-Oct-05 or later
5 (the contents of which are also included in zip.h) for terms of use.
6 If, for some reason, both of these files are missing, the Info-ZIP license
7 also may be found at: ftp://ftp.cdrom.com/pub/infozip/license.html
8 */
9 /*
10
11 This is an Important note about pathnames
12
13 */
14
15 static char DuplicVolumeNote[] = {
16 "\rIMPORTANT NOTE:" \
17 "\r" \
18 "\r This port has one weak point: It is based on pathnames !! " \
19 "\r Because it's a port !! Unlike MacOS: As far as I know all other "\
20 "\r Operatingsystems (eg.: Unix, DOS, OS/2, ...) are based on pathnames" \
21 "\r " \
22 /* a short quote from "Inside Macintintosh, Files"; slightly modified by me */
23 "\r On a Mac: Files and directories located in the same directory " \
24 "\r must all have unique names. However, there is no requirement " \
25 "\r that volumes have unique names. It is perfectly acceptable for two mounted" \
26 "\r volumes to have the same name. This is one reason why a application should " \
27 "\r use volume reference numbers rather than volume names to specify volumes," \
28 "\r but for this Zip-Port I can't use reference numbers. " \
29 "\r " \
30 /* end quote */
31 "\r" \
32 "\r From the developers point of view:"\
33 "\r The use of pathnames, however, is highly discouraged. If the user changes"\
34 "\r names or moves things around, they are worthless." \
35 "\r Full pathnames are particularly unreliable as a means of identifying files," \
36 "\r directories or volumes within your application," \
37 "\r for two primary reasons:" \
38 "\r" \
39 "\r* The user can change the name of any element in the path at" \
40 "\r virtually any time." \
41 "\r* Volume names on the Macintosh are *not* unique. Multiple" \
42 "\r mounted volumes can have the same name. For this reason, the use of" \
43 "\r a full pathname to identify a specific volume may not produce the" \
44 "\r results you expect. If more than one volume has the same name and" \
45 "\r a full pathname is used, the File Manager currently uses the first" \
46 "\r mounted volume it finds with a matching name in the volume queue." \
47 "\r" \
48 "\r" \
49 "\r The main reason is that an attempt to implement support exact saving of" \
50 "\r the MacOS specific internal file-structures would require a throughout" \
51 "\r rewrite of major parts of shared code, probably sacrifying compatibility" \
52 "\r with other systems." \
53 "\r I have no solution at the moment. The port will just warn you if you try" \
54 "\r zip from / to a volume which has a duplicate name." \
55 "\r MacZip has problems to find the archives and files." \
56 "\r" \
57 "\r" \
58 "\r ... and the moral of this story:" \
59 "\r" \
60 "\r Don't mount multiple volumes with the same " \
61 "\r name while zip/unzip is running" \
62 "\r and "\
63 "\r My (Big) recommendation: Name all your volumes with a unique name "\
64 "\r (e.g: add a space character to the name) and" \
65 "\r MacZip will run without any problem." \
66 "\r" \
67 "\r" \
68 "\r Dirk Haase" \
69 };