Request to Create account for contribution

[Sachin T]

Hi,
Thank you for reviewing our patches and sharing your feedback.
I’d like to clarify a few points and provide some updates:

  1.  Platform-related changes: The patches we shared are still a work in progress. Our intention is to introduce z/OS-specific changes in a clean and maintainable way, and we’re fully open to collaborating with you to ensure these updates don’t negatively impact other platforms. We welcome any suggestions on how best to structure or isolate z/OS changes.
  2.  License: Thank you for pointing this out. We've updated our patches to use the GPL license as expected and will ensure all future contributions follow the licensing requirements of the respective GnuPG components.
  3.  Linux on Z vs. z/OS: There may have been some confusion regarding platform support. While Linux on Z (s390x) is already supported upstream, our work targets z/OS, which is a distinct operating system with its own runtime environment and system interfaces. The patches we’re contributing are specifically for enabling GnuPG to build and run on z/OS.
Our goal is to work closely with you to refine and upstream these changes in a way that benefits the broader community. Please let us know how we can best proceed.
Regards
Sachin


On 08/05/25, 2:13 PM, "Werner Koch" <wk at gnupg.org> wrote:
Hi!

On Wed,  7 May 2025 15:14, Sachin T said:

> I hope you’re doing well. I need to register an account to contribute
> patches related to IBM z/OS platform

Done.

> As part of the zOpen community https://github.com/zopencommunity),
> where we work on porting open-source tools to z/OS.  As part of this

And I though we don't need that anymore due to the available of Linux on
thatatform.  In fact some very old code to handle EBCDIC has already
been removed and we meanwhile assume UTF-8 encoding for everything.

I had a quick look at some patches and I am missing any documentation
for the patches.   Random example:

     case GNUPG_MODULE_NAME_CONNECT_AGENT:
-      X(bindir, "tools", "gpg-connect-agent");
+#if __MVS__
+       X(bindir, "bin", "gpg-connect-agent");
+#else
+       X(bindir, "tools", "gpg-connect-agent");
+#endif

Why do you need to change this?  The second arg is the build directory
and only used for internal build and regression test purposes.

Patches like

-     (pipe:gpg `(--yes -ea --recipient ,usrname2))
+     (pipe:gpg `(--yes -ea --recipient ,usrname2 --trust-model always))

Are not useful because that can't be a platform issue.  A patch to
configure is a no-go becuase configure is a built file.

   AC_CHECK_HEADER(zlib.h,
-     AC_CHECK_LIB(z, deflateInit2_,
+     AC_CHECK_LIB(z, deflate,

Is also not good because it breaks on existing platforms.  You need to
test for deflate only after you checked that deflateInit2_ does not exists.

The patches seem to be under a BSD license.  We can't accept this.  The
whole thing seems to be under Apache 2.0 License - this is incompatible
to the GPL; sorry.


Shalom-Salam,

   Werner

--
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250517/a547929e/attachment-0001.html>