[Info-vax] Curl, zLib and VSI V8.4-1H1 Kit Dependency Issue

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Sat Jan 2 11:47:54 EST 2016


On 2016-01-02 14:47:37 +0000, Kerry Main (Personal) said:

> 
> "PCSI-W-SFTREF, product VMSPORTS I64VMS ZLIB V1.2-8 referencesproduct 
> HP I64VMS VMS"
> ...
> Thoughts on how to address?


Yeah; that'll happen.   Two choices: PRODUCT REGISTER the HPE product.  
  Skim PCSI$REGISTER_PRODUCT.COM for details on that approach.   Or 
extract the files from the ZLIB kit, fix the PDF to accept either VSI 
or HPE products, and rebuild the kit.

We're all going to be doing that more often, unfortunately.

VSI will hopefully deign to describe how they envision this vendor 
migration actually working.   Whether it's some sort of hypothetical 
/OPTIONS=VENDOR_OVERRIDE=HPE_VSI or otherwise.  Check the HELP and see 
if VSI added something — they claimed to be working on this problem 
within PCSI, but I never bothered following up.   Because without some 
guidance, folks are typically going to solve this differently.  Or 
they're not going to use something VSI has or will add.  (And because 
once V8.4-2 is out — if it has "a better way to do this" — then more 
than a few of us will assume that VSI V8.4-1H1 will likely be pretty 
quickly dead and not bother with this stuff.)

Though inappropriate for an expedient get-the-release-out environment 
such as what VSI had for V8.4-1H1 and likely also have for V8.4-2, PCSI 
and other user-mode VMS tools have been suffering from the lack of a 
relational database package within OpenVMS, too.   Those are way easier 
to deal with these cases, then the usual punched card emulation of RMS 
records.   The lack of the database and the necessary expediency will 
probably lead to increasing the size of the existing code quagmire, 
unfortunately.


Just noticed this cut-and-paste boo-boo in the HELP from OpenVMS I64 
V8.4 UPDATE 10, too:

PRODUCT

  INSTALL

    Description

         To uninstall complete products, including any patches or
         mandatory updates that might have been applied to them, use the
         PRODUCT REMOVE command.

         To uninstall patches or mandatory updates while still retaining
         the original product that was installed, use the PRODUCT UNDO
         PATCH command. However, to use PRODUCT UNDO PATCH, you must have
         created and retained recovery data sets for these patches. (By
         default, the PRODUCT INSTALL command creates a recovery data set
         when patch kits are installed.)

         For more information about the use of recovery data sets, see the
         description of the PRODUCT UNDO PATCH command.




-- 
Pure Personal Opinion | HoffmanLabs LLC




More information about the Info-vax mailing list