VSI-AXPVMS-VGIT-V0009-9-1-RELNOTE.PDF

Order Number: XX-7EF6D-A2

This document describes VGIT V0.9-9, a partial Git implementation designed for VSI OpenVMS Alpha and I64 systems. Its primary purpose is to enable OpenVMS developers to use Git functionality and interact with cloud-based version control services like GitHub and BitBucket.

Key updates in this release (V0.9-9) include improved $STATUS handling for DCL/MMS scripts, a fix for rare file skips during commit, added handling for pull conflicts, a quiet clone option (-q), and the removal of credentials from merge messages. Previous updates enhanced various Git commands (e.g., checkout, commit, rm) to be more Git-like, improved branching and merge support, fixed issues with cloning from Microsoft Azure DevOps, resolved lockfile errors, and updated the certificate bundle.

Requirements: VGIT requires OpenVMS 8.4-1H1 or higher and a compatible TCP/IP stack (VSI TCP/IP, HPE TCP/IP Services, or MultiNet). OpenSSL 1.1.1b is statically linked, making a separate VSI SSL111 installation unnecessary.

Installation & Setup: Installation is performed via an OpenVMS PCSI kit using PRODUCT INSTALL VGIT. Post-installation, users must configure specific logical names in SYS$MANAGER:SYSTARTUP.COM, SYSHUTDWN.COM, and SYSLOGIN.COM. The CA-BUNDLE.CRT file (certificate bundle) is crucial for interacting with cloud services and needs to be maintained. Initial configuration involves setting user details (vgit config user) and, if needed, proxy settings (vgit2 config http.proxy).

Important Considerations:

  • All files operated on by VGIT must be in stream-lf format.
  • VGIT exclusively functions on ODS-5 file systems.
  • Some VGIT commands are case-sensitive.
  • Initial cloning of large repositories might be slow.
  • For key-based authentication, GIT$ID_RSA and GIT$ID_RSA_PUB logical names must be defined.
  • To force username/password authentication, define the GIT$FORCE_CREDTYPE_USERPASS_PLAINTEXT logical name.
  • VGIT supports OpenVMS clusters for shared primary repositories.
  • Users should be cautious about logical names that might conflict with repository names.
XX-7EF6D-A2
May 2000
6 pages
Quality

Original
0.6MB

Site structure and layout ©2025 Majenko Technologies