Annotation of embedaddon/curl/packages/vms/curl_release_note_start.txt, revision 1.1.1.1
1.1 misho 1: From file: CURL_RELEASE_NOTE_START.TXT
2:
3: Note: These kits are produced by a hobbyist and are providing any support
4: or any commitment to supply bug fixes or future releases. This code is
5: as-is with no warrantees.
6:
7: The testing of this build of curl was minimal and involved building some of
8: the sample and test programs, accessing a public HTTPS: website, doing a
9: form post of some VMS test files, and FTP upload of some text files.
10:
11: Due to the way that PCSI identifies packages, if you install a package from
12: one producer and then want to upgrade it from another producer, you will
13: probably need to uninstall the previous package first.
14:
15: OpenVMS specific building and kitting instructions are after the standard
16: curl readme file.
17:
18: This product may be available for your platform in a PCSI kit. The source kit
19: contains files for building CURL using GNV or with a DCL procedure.
20:
21: The GNV based build creates a libcurl share imaged which is supplied in the
22: PCSI kit.
23:
24: This version of CURL will return VMS compatible status codes when run from
25: DCL and Unix compatible exit codes and messages when run with the SHELL
26: environment variable set.
27:
28: This port of Curl uses the OpenSSL, Ldap, and Kerberos V5 that are bundled
29: with OpenVMS or supplied as updates by HP. Ldap and Kerberos are not available
30: on the VAX platform. See section below for a special note about HP OpenSSL
31: on Alpha and IA64.
32:
33: The supplied CURL_STARTUP.COM procedure that is installed in
34: [VMS$COMMON.SYS$STARTUP] can be put in your VMS startup procedure to install
35: the GNV$LIBCURL shared image and create logical names GNV$LIBCURL to reference
36: it. It will create the GNV$CURL_INCLUDE logical name for build procedures
37: to access the header files.
38:
39: Normally to use curl from DCL, just create a foreign command as:
40: curl :== $gnv$gnu:[usr.bin]gnv$curl.exe
41:
42: If you need to work around having the older HP SSL kit installed, then
43: for DCL create this command procedure:
44:
45: $ create/dir gnv$gnu:[vms_bin]/prot=w:re
46: $ create gnv$gnu:[vms_bin]curl.com
47: $ curl := $gnv$gnu:[usr.bin]gnv$curl.exe
48: $ define/user ssl$libcrypto_shr32 gnv$curl_ssl_libcryptoshr32
49: $ curl "''p1'" "''p2'" "''p3'" "''p4'" "''p5'" "''p6'" "''p7'" "''p8'"
50: ^Z
51:
52: Then you can use: curl :== @gnv$gnu:[vms_bin]curl.com to run curl.
53:
54: For the HP SSL work around to work for GNV do the following:
55: $ create/dir gnv$gnu:[usr.local.bin]/prot=w:re
56: $ create gnv$gnu:[usr.local.bin]curl.
57: #! /bin/sh
58: dcl @gnv\$gnu:[vms_bin]curl.com $*
59: ^Z
60:
61: Similar work arounds will be needed for any program linked with GNV$LIBCURL
62: until the HP OpenSSL is upgraded to the current 1.4 version or later.
63:
64: If you are installing a "daily" build instead of a release build of Curl, some
65: things have been changed so that it can be installed at the same time as
66: a production build with out conflicts.
67:
68: The CURL_DAILY_STARTUP.COM will be supplied instead of CURL_STARTUP.COM.
69: This file is actually not used with the daily package and is provided as
70: a preview of what the next CURL_STARTUP.COM will be for the next release.
71: Do not run it.
72:
73: The files that are normally installed in [VMS$COMMON.GNV.usr], for the
74: daily build are installed in [VMS$COMMON.GNV.beta] directory.
75:
76: To use the daily GNV$LIBCURL image, you will need to define the logical
77: name GNV$LIBCURL to the image.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>