Re: How to distribute Rexx helpfiles?
|
On Mon, Nov 4, 2024 at 4:18?PM Mark Waterbury via <mark.s.waterbury= [email protected]> wrote: How are you packaging and delivering the actual code for distribution currently?
bREXX has an established practice for distribution, which I have repeated for the upcoming release.? The code is built completely on GitHub (including launching VM/370 under Docker to compile it!), then packaged in three forms: - A pair of "binary" and "source" AWS tape files.
- A pair of "binary" and "source" VMARC files.
- A replacement for the GCCBRX DASD file of VM/370 CE.
The AWS tapes and VMARC files contain the exact same set of CMS files.? The DASD file is, of course, somewhat different,?but the minidisks on it contain the files that were dumped for the first two formats.
?I would create a VMARC archive file that contains all of those help files that need to go on the MAINT 19D minidisk, with instructions so anyone can sign-on as MAINT, access 19D as R/W, and then VMARC UNPACK them to that disk.
Thanks, that's a good option.
? You (or someone) could upload this VMARC file to the "Files" area of this H390-VM list group.
I'd probably distribute it from GitHub along with the rest of bREXX, so at least it could be versioned.
?I would also add them to that github.
Makes sense.
Thanks!
Ross
|
