New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix VMS installation #16842
Fix VMS installation #16842
Conversation
Currently a draft, until I've verified that it works as expected |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go ahead with authenticity of verification.
1892ca8
to
0f7016d
Compare
c17cd8d
to
0c63363
Compare
I've tested this today, it seems to work like it's supposed to, so not a draft any more. I'll run a few more tests on Sunday |
Ping! This really should end up in the upcoming release update |
The program name version info is supposed to be the major release version number. This was forgotten when the versioning scheme was changed for 3.0, so the minor release version number slipped in as well.
Configurations/descrip.mms.tmpl uses $target{pointer_size}, not $config{pointer_size}, so the same should be used in installation scripts, for consistency.
Also, the modules installation directory is version agnostic on other platforms, there's no real reason why it shouldn't be on VMS.
…istently It's used in Configurations/descrip.mms.tmpl, but was forgotten in the VMS installation scripts.
The logical name for the engines directory is named one way in VMS/openssl_startup.com.in, but a different name was deassigned in VMS/openssl_shutdown.com.in.
…ms.tmpl This was part of 0cbb6f6, but was incomplete in that commit.
0c63363
to
b7a3ca1
Compare
Agree urgent |
The program name version info is supposed to be the major release version number. This was forgotten when the versioning scheme was changed for 3.0, so the minor release version number slipped in as well. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842)
Configurations/descrip.mms.tmpl uses $target{pointer_size}, not $config{pointer_size}, so the same should be used in installation scripts, for consistency. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842)
Also, the modules installation directory is version agnostic on other platforms, there's no real reason why it shouldn't be on VMS. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842)
…istently It's used in Configurations/descrip.mms.tmpl, but was forgotten in the VMS installation scripts. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842)
The logical name for the engines directory is named one way in VMS/openssl_startup.com.in, but a different name was deassigned in VMS/openssl_shutdown.com.in. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842)
Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842)
Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842)
Pushed to openssl-3.0 and master. There was a trivial conflict in the CHANGES.md file when cherry-picking to master, which I resolve during the merge. |
The program name version info is supposed to be the major release version number. This was forgotten when the versioning scheme was changed for 3.0, so the minor release version number slipped in as well. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842) (cherry picked from commit 3c9293b)
Configurations/descrip.mms.tmpl uses $target{pointer_size}, not $config{pointer_size}, so the same should be used in installation scripts, for consistency. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842) (cherry picked from commit e30545e)
The logical name for the engines directory is named one way in VMS/openssl_startup.com.in, but a different name was deassigned in VMS/openssl_shutdown.com.in. Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from #16842) (cherry picked from commit 73e47e3)
An effort was made to update the VMS installation data to align with configuration data. This touched the script templates in VMS/, but didn't update the generation of vmsconfig.pm to match... and also missed a spot. This change adds the missing updates Ref: openssl#16842 Fixes openssl#22899
An effort was made to update the VMS installation data to align with configuration data. This touched the script templates in VMS/, but didn't update the generation of vmsconfig.pm to match... and also missed a spot. This change adds the missing updates Ref: openssl#16842 Fixes openssl#22899
An effort was made to update the VMS installation data to align with configuration data. This touched the script templates in VMS/, but didn't update the generation of vmsconfig.pm to match... and also missed a spot. This change adds the missing updates Ref: #16842 Fixes #22899 Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> (Merged from #23081)
An effort was made to update the VMS installation data to align with configuration data. This touched the script templates in VMS/, but didn't update the generation of vmsconfig.pm to match... and also missed a spot. This change adds the missing updates Ref: #16842 Fixes #22899 Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> (Merged from #23081) (cherry picked from commit 4058e12)
An effort was made to update the VMS installation data to align with configuration data. This touched the script templates in VMS/, but didn't update the generation of vmsconfig.pm to match... and also missed a spot. This change adds the missing updates Ref: #16842 Fixes #22899 Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> (Merged from #23081) (cherry picked from commit 4058e12)
An effort was made to update the VMS installation data to align with configuration data. This touched the script templates in VMS/, but didn't update the generation of vmsconfig.pm to match... and also missed a spot. This change adds the missing updates Ref: #16842 Fixes #22899 Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> (Merged from #23081) (cherry picked from commit 4058e12)
An effort was made to update the VMS installation data to align with configuration data. This touched the script templates in VMS/, but didn't update the generation of vmsconfig.pm to match... and also missed a spot. This change adds the missing updates Ref: openssl#16842 Fixes openssl#22899 Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> (Merged from openssl#23081) (cherry picked from commit 4058e12)
Fix VMS installation
VMS installation scripts were forgotten in the 3.0 release, most of
them have remained as they were for 1.1.1, when the new versioning
scheme should have been reflected in these as well.
Furthermore, the IVP is amended to check the presence of the standard
OpenSSL providers.