ports, mentioning in particular that even if you downloaded a
_release_ source archive these particular ports are not considered
to be of release quality.
git-svn-id: svn://svn.tartarus.org/sgt/putty@5583
cda61777-01e9-0310-a592-
d414129be87e
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is a port of PuTTY to the Classic Mac OS. It is a work in
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This is a port of PuTTY to the Classic Mac OS. It is a work in
-progress and should be considered unfinished and insecure. Unless you
+progress and should be considered unfinished and insecure. It is
+not considered to be of release quality, even if you found it (and
+you're reading this) in a PuTTY release source archive. Unless you
know what you're doing, don't use it.
Compiling it:
know what you're doing, don't use it.
Compiling it:
This directory contains a Mac OS X port of PuTTY/pterm, running as a
native Aqua GUI application.
This directory contains a Mac OS X port of PuTTY/pterm, running as a
native Aqua GUI application.
-THIS PORT IS CURRENTLY UNFINISHED AND EXPERIMENTAL. You are welcome
-to use it, but don't be surprised at unexpected behaviour. I'm not
-kidding.
+THIS PORT IS CURRENTLY UNFINISHED AND EXPERIMENTAL. It is _not_
+considered to be of release quality, even if you've found it (and
+are reading this) in a PuTTY release source archive. You are welcome
+to try using it, but don't be surprised at unexpected behaviour. I'm
+not kidding.
In particular, I have not yet decided where OS X PuTTY should store
its configuration data. Options include storing it in ~/.putty to be
In particular, I have not yet decided where OS X PuTTY should store
its configuration data. Options include storing it in ~/.putty to be